uranian
Joined 9 years ago
Joined 9 years ago
If there is a slow death to guitar than it is because it's almost impossible to earn any money with it, except for the lucky few. Learning an instrument like guitar takes many, many years, which is quite a hobby.. If you would spend the same amount of time in learning software development you are almost assured to have a solid income as result.
if (__guard__(does.that != null ? does.that.prop : undefined, x => x.exist)) { console.log('yes, no crash!'); }
function __guard__(value, transform) {
return (typeof value !== 'undefined' && value !== null) ? transform(value) : undefined;
}
oh my..This was 1 line of CS, how to clean this up without a chance of creating bugs?
How on earth is ESxxx an improvement on CS anyways? It's just not true, it's a leap back.
> Producing readable code is certainly the intent!
This is hilarious! Transpiling from the most readable JS alternative to ES6? Then you need to clean up some things, making it ready for yet another transpiler called Babel? And then everything is OK?
Show me how you are going to make this pretty:
if does.that?.prop?.exist then console.log 'yes, no crash!'There is also a nice comment in here about a large project that became a misery because of TS. Think twice before you hope!
No! It seems you've never learned Coffeescript well enough to know the differences, just like too many other ES6 proponents.
Maybe on a slow pc, but with Atom on my macbook pro I have no performance issues at all period. I code 8+ hours a day (for many years), and no my fan is not spinning all the time because of Atom. I have 16Gb ram, have multiple apps open at the same time, Chrome with 30+ tabs, listen music via youtube, etc..
I was a long time Sublime user, but the $70 they're asking is really way too much with so many great open source alternatives today. Would they at least divide the $70 to all the package writers that actually make Sublime a great editor I might be willing to spend it, but unfortunately they want all the money for themselves..
Switched to Atom a while ago, I gained (some really great) features and finally got rid of the trial pop-up.
Thank you Jaques Fresco for opening my eyes to this and RIP.
I am more concerned that the code that runs during a re-render is not rebuilding huge static lists that never change and so. I see that over and over again in React apps. I tend to build a lot of the static stuff in the ComponentWillMount stage to prevent that. Only when already optimised code is getting to slow I start thinking about preventing re-rendering if possible.
My reason for not starting with ShouldComponentUpdate is that you have to be very careful not creating nasty bugs with that like I did some times. If a year later you write some code and it doesn't work for some reason it is painful if you find out after a long search that a stupid child component did not update for some prevention rule you forgot about. I really try hard to avoid premature optimisations.
For apps that don't run on Linux for now, like Adobe, I'd rather move to OSX. Only reason for me to install Windows would be some obscure game that only runs on that platform. I honestly cannot think of any other reason to install Windows.
Windows doesn't even come close to the reliability and comfort of my macbook-pro. I was always reluctant to move to osx, but I have to admit, this is simply the very best and most reliable machine I've ever had! It never crashed once, while I push it to it's limits every day!