winteriscomming

5 ms·

1.
by winteriscomming 14y ago
Please save us from JavaScript, google.
2.
by winteriscomming 14y ago
It is just much more difficult to have tooling since the tools cannot know for sure what the program is doing (and neither can another human looking at it).
3.
by winteriscomming 14y ago
You are entitled to your opinion but many developers disagree and want some more structure in the programming model. The very fact that many people are trying so hard to come up with some solution to JS means that there are significant pro
4.
by winteriscomming 14y ago
Go to function definition, refacor/rename, find references, view object / class hierarchy, and so on. Why not have all this work 100% of the time? Tooling makes your life so much easier. I don't understand why people would resist optional
5.
by winteriscomming 14y ago
Because these "loose and freeform" attributes make your life hell building large applications with large teams.
6.
by winteriscomming 14y ago
I agree. Visual design is like fashion and flatter is now "in". There are pros (cleaner, less distracting chrome) and cons (where is the button).
7.
by winteriscomming 14y ago
I feel like on the overly skeuomorphism to overly flat / no affordances spectrum, Android Jellybean is striking the right balance. It's modern and clean and flat but doesn't take it as far as windows 8 where everything is text, a rectangle
8.
by winteriscomming 14y ago
The class made total sense to me. This is common stuff in enterprise software world.
9.
by winteriscomming 15y ago
Both make my Core i7 CPU go to 100% for a simple animation of 100 small circles. I thought HTML5 was going to solve all performance problems and make me breakfast too. Wonder if this will even run on mobile.
10.
by winteriscomming 15y ago
No I don't but my point is that 2 years seems a bit slow as far as evolution of JS is concerned.
11.
by winteriscomming 15y ago
Is it really not out for 2 years? Really? That seems like a long time for not that much changes. Any improvement is welcome, but still. I don't know if this will keep pace with Dart and other options. It seems way too slow.
12.
by winteriscomming 15y ago
People love new things and the story of the new guy overtaking the evil status quo. Node and JS in general seems very hyped right now. Every day there is a new blog about accomplishing something in these technologies that was entirely pos
13.
by winteriscomming 15y ago
Yes I like the direction dart is going in (except would prefer the type system had more actual meaning than just annotations for tooling, but still). My pipe dream: - Google implements a VM for dart or equivalent. - Dart, Java, C#, ActionS
14.
by winteriscomming 15y ago
No real classes. No type systen (optional at least would be good). No packages. No modules. No generics. No annotations, mix-ins, actors. No properties. No interfaces. No abstract classes. Horrible to maintain on large projects. H
15.
by winteriscomming 15y ago
There is a increasing trend: many people do not want to code in JavaScript. This is happening because more and more engineers with experience in other languages are forced to deal with JS now days and they are trying to come up with alter
16.
by winteriscomming 15y ago
I don't think you can dismiss someones dislike for a language as "they don't know how to use it". Common, many people have been building applications on client and server for 15+ years using JS and whatever exists on the backend. And 90%
17.
by winteriscomming 15y ago
Agreed.
18.
by winteriscomming 15y ago
JS has lots and lots of fundametal issues. Weird OO implementation (argue all you want but prototype inheritance is not what the prevailing wisdom is on how to do OO), no type system (at least give the option!), no packages/modules, no gen
19.
by winteriscomming 15y ago
A byetcode/VM approach would be an improvement on the web client. This has been used successfully for 10+ years on the server (JVM, CLR), so why not learn from things and advance the state of web development. I don't understand why people