HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
magento
magento2
PHP2013–2021
magento / magento2

magento2

Prior to making any Submission(s), you must sign an Adobe Contributor License Agreement, available here at: https://opensource.adobe.com/cla.html. All Submissions you make to Adobe Inc. and its affiliates, assigns and subsidiaries (collectively “Adobe”) are subject to the terms of the Adobe Contributor License Agreement.

12Distinct people
16Mentions
0Explicit recommenders
12.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Prior to making any Submission(s), you must sign an Adobe Contributor License Agreement, available here at: https://opensource.adobe.com/cla.html. All Submissions you make to Adobe Inc. and its affiliates, assigns and subsidiaries (collectively “Adobe”) are subject to the terms of the Adobe Contributor License Agreement.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 7:24:48 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year16 dated mentions

Observed mentions: 2013-11-21 17:54:45 UTC to 2021-04-07 11:48:09 UTC.

012342013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20132014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC110
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC101
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC404
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC202
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC211
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC404
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101

What Hacker News says

4 sources
The main issue with BigCommerce is that they do not offer any compelling advantage over existing open source system. Moreover being a loss making entity like Shopify without any sticky system like marketplace which drives traffic, I doubt there is much value in it except that investors wants to cash-out given the current unrealistic stock market. In case a company use magento [1], Saleor [2], Sylius [3], Shuup [4], Solidus [5], Spree [6] combined with vue-storefront [7], storefront UI [8] and openflutttercommerce app [9] the amount of efforts to build a highly resilient and functional system is cheaper with complete control over customer, supply chain, pricing, product, marketing, sales and promotion data. Also the efforts will be similar to using shopify, bigcommerce with more cost-savings. Indeed shopify itself use many components from
Read the rest
rails eco-system built by Spree and Solidus community. Its very easy to build a highly customized and resilient system using cloud offering combined with these open source systems. So I do not see why a mid-size business will choose shopify or bigcommerce. They are good for mom-pop shops and simple commerce, but for unique shopping experience they fall short and better to build customized one with complete control. [1] https://github.com/magento/magento2 [2] https://github.com/mirumee/saleor [3] https://github.com/Sylius/Sylius [4] https://github.com/shuup/shuup [5] https://github.com/solidusio/solidus [6] https://github.com/spree/spree [7] https://github.com/vuestorefront/vue-storefront [8] https://github.com/Divanteltd/storefront-ui [9] https://github.com/4seer/openflutterecommerceapp
In BigCommerce S1
But it's not a hint to the compiler. It's stating a fact to the compiler. It'll stop compilation. If I have a basket of fruit, all the items in that basket container are fruit. I can't put anything other than fruit in it. It's a basket of fruit. I know how to interact with the fruit due to its type. If I am able to put dung into my basket, my fruit is spoiled and I cannot assume how to interact with the objects in the basket. This is a PHP array without types at the array level. I can put dung into it and have no idea how to interact with it. Or are you saying that a container of any type is perfectly acceptable? Did the other languages (C++, C#, Java) get it wrong? eg. on this line can you tell me what the array holds and how I interact with it? What does array $operations hold? https://github.com/magento/magento2/blob/420a8b6209a4e62ede
Read the rest
In A look at modern PHP
How do you know how you got to that point in the code without a debugger? What's the call stack like? How could you debug a call in a DLL that is being loaded by your program if you do not use a debugger? It might be alright for tiny programs but it's essential for "big" applications. printf'ing isn't going to help with 2 million+ lines of code or where there's a leak somewhere in that code (eg. someone else wrote some bad code or bad reference counting and didn't release when they should, eg. in COM wrappers in Windows), or someone is double-freeing some memory or trampling on memory and you need a hardware breakpoint to know what is modifying that memory at any given point. This doesn't affect just compiled languages either - how would you know what is constructing this object, for example? https://github.com/magento/magento2/blob/420a8
Read the rest
b6209a4e62ede9... EDIT: I say all this in a generic "use of debugger" sense, not a Go-specific debugger usage.
In Go's Tooling Is an Undervalued Technology

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.