111–120 of 235 posts
"Special shout out to Yehuda Katz, who helped us design the annotation+decorator proposal which helped make this work possible." How in the world does this man keep up with all these projects? He needs to write a book on motivation.
Earlier quoted context omitted.
Probably, but that's a legitimate concern. Even with Microsoft's recent open source moves (which I think are pretty awesome), we've had a history of having Microsoft force languages and extensions down our throat in an attempt to usurp the open web and standards: ActiveX, VBScript in IE, .hta's, Silverlight, etc. The counter to that is that TypeScript is Apache-licensed. However, you can't erase history by throwing u…
Ironically your comment could be taken as a classic example of the kind of FUD Microsoft used to spread. You give examples from the past that, you admit, clearly don't apply. You talk about "feels less open" when it is factually not. You speculate on others (who are they?) being pushed past a tipping point. Doubt, doubt, doubt and fear, fear, fear when in fact there's nothing you can point to in reality to back it up…
Not only are these strategic moves, they are strategic moves by a large company aimed at competing with people like me who develop software on multiple platforms and contribute, unpaid, to an open software ecosystem.
Is javascript really so bad? Edit: Why did this question get down voted? It was an honest question...
Any dynamically typed language is absolutely horrible once you break a certain line count.
Is javascript really so bad? Edit: Why did this question get down voted? It was an honest question...
Yes, it is really, really, really bad. http://wtfjs.com Whole web is a mess and people are trying to monkey-patch it.
That has been true for the last 20+ years, but it gets less and less accurate as time goes on. The web today is way less messy than it was even 3 years ago. The way we write JS is way less messy, the way we write CSS is way less messy. Standards have improved, lighten up.
Are there any organized efforts to fork the 1.x branch to sustain existing applications?
[1] Mentioned in the ng-conf keynote IIRC, but this was also told to me directly by one of the Angular core team members when I spoke with him today.
Embrace, extend, extinguish.
Also, the EEE accusation doesn't really apply to open source projects. EEE is bad since after the proprietary product supersedes ("extinguishes") an open product, the community loses control forever. However when an open product supersedes another, the community always have the choice of forking the project to take back control.
"Special shout out to Yehuda Katz, who helped us design the annotation+decorator proposal which helped make this work possible." How in the world does this man keep up with all these projects? He needs to write a book on motivation.
By dumping them mid-way and getting to the next shiny one?
Anybody knows how this RoR kickstarter project finally went?