Re:The State of Meteor Part 1: What Went Wrong
by ams6110 on Wednesday January 20, 2016 @10:33AM
(#10938718)
It's why PHP still thrives.
Re:The State of Meteor Part 1: What Went Wrong
by explorer666 on Wednesday January 20, 2016 @11:43AM
(#10939320)
Or because it's a mature language, with a robust, very rich and up-to-date ecosystem.
Re:The State of Meteor Part 1: What Went Wrong
by bpicolo on Wednesday January 20, 2016 @07:15PM
(#10942470)
It's really not very rich and up-to-date, in my opinion. In my experience, the vast majority of oss PHP projects started a decade ago, and they all keep certain back-compat, so they run with the drag of old paradigms. Actual new contribution to the ecosystem seems almost impossible to find, and there's a lot of areas that simply aren't great.
E.g try to find a sane way to work with PostgreSQL json,jsonb columns in a safe way in php. There's no even halfway decent solution. Half-supported, roll-your-own in doctrine is the best you can get
Re:The State of Meteor Part 1: What Went Wrong
by explorer666 on Thursday January 21, 2016 @02:57PM
(#10947847)
> It's really not very rich and up-to-date, in my opinion. In my experience, the vast majority of oss PHP projects started a decade ago, and they all keep certain back-compat, so they run with the drag of old paradigms. Actual new contribution to the ecosystem seems almost impossible to find, and there's a lot of areas that simply aren't great.
100% false.
I see people make this mistake over and over again. It's so easy to underestimate the cost of learning something new. Often times it's best to just go with what you already know until you've done enough non-mission critical in the shiny new thing to be confident in it.