uranian

I once started with DOS, moved to windows, linux (various distro's), now already for a few years on osx.

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!

I think the drop in revenue is because the market is really saturated. All those millions of guitars produced are not destroyed, it's not the kind of product that you can apply 'planned obsolescence' to. Instead, the vintage one's are often better sounding and therefore more popular. Also, if you find a good vintage guitar you are almost assured it will remain good as the wood has proven to be stable.

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;
  }

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.

Sorry, no weird hostility, just an observation. The weirdness comes more from the way how you guys think about creating a typed language. What the heck would a CS compiler with static type checking have to do with var statements apart from generating them in the final JS as it does now already?

You mean only ES2016 from that list?

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!'

Instead of wanting projects to move to a language you know, you can better first learn the language they are written in, and try to understand their decision in the first place. If you know CS very well you would not be so eager to move to Babel transpiler imao.

There is also a nice comment in here about a large project that became a misery because of TS. Think twice before you hope!

it has all of Coffeescript features and more

No! It seems you've never learned Coffeescript well enough to know the differences, just like too many other ES6 proponents.

$70 is nothing compared with the performance that you get.

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.

This is a true loss for the world. Although his revolutionary ideas were IMHO by times a little over the edge, he envisioned and fought for a world without poverty and war, where earth's resources are not being depleted by hunger for money and power; A resource based economy.

Thank you Jaques Fresco for opening my eyes to this and RIP.

For some reason the focus is always on preventing re-rendering if it comes to optimising a React app. I understand that it can be really effective and is often the easy way out, but re-rendering in itself is not costly and I don't really care about it the most of the time.

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.

I didn't say all people who use it are idiots. But willingly sharing your private data for free while waiving all your rights? If you realise that facebook runs AI on that data and knows much more about you then you could ever imagine, and if you realise they are selling that data to companies you might not like so much, or what else more, that's pretty stupid imao.

You should have learned to be very happy they disabled your account! Facebook is for idiots and for companies that milk those idiots. This event likely saved you for wasting even more of your precious life time. Be happy and do some great things with your life without feeling the need to constantly show off.

Turning off Windows update is not enough I'm afraid. Better remove this misery-ware completely from your pc and move to Linux. Linux is better, safer, cheaper, and more fun overall!

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.

It's not wrong, just feels misleading. For me it's like Sublime text comes with a little tutorial with the title "Get started making apps", and only give an intro on making a hello world program in C++, to sell their product.

No, qwerty for keyboards is more like the lay out of the 12 notes on an instrument, and there are many instruments.

Music notation is more like a programming language. The score is like a program that you can read/interpret and play.

Making music (also EDM) is really, really hard. Most people that try will fail, and Ableton knows that. They are just trying to sell their product here which is fair enough. But 'getting started making music' is like you only need their product, trigger some samples and you can be an artist too.

Try sit behind a drum kit for the first time, you think you can start making music? Most aspiring drummers need to practice for years before you can play a reasonable beat. Same with EDM, it takes many years of practice and improving all kinds of skills. This tutorial is just showing how you can trigger samples in a grid and how you can put this together in a DAW. For me that is not making music, sorry.

Btw, the resulting loops in the tutorial were not made by beginners, and listen to the result, is that music to you? Would you buy that? Another title that would be appropriate but not sell, could be: Get started making rubbish.

Yes, studied music on the conservatorium and have been a professional producer for years doing pop and edm etc.. Used most of the known DAW's from FL to ProTools.

A more appropriate title would be: Get started triggering samples.

Making music is really something different IMO.

Reading the comments I have to consider myself very lucky in a way. I work full-remote.

- I never use an alarm, normally waking up around 8:30am

- I often start coding right away when I wake up, in these first 2 hours I am often exceptionally productive

- eat something, coffee, reading, relaxing

- do some more coding till I feel my focus drops

- repeat the last two steps

When I feel tired I try not to code if possible, I consider it being a bad habit.

Relaxing between the focussed coding sessions is of major importance to produce good code IMHO, while relaxing I'm often thinking about the different options of how I can best write the next piece of code.

If I have a bad day, not being really productive, I often do some more coding at night if I can get the right focus.

On a good day I outperform 2 coders that work in the open office of our company, with ease.

Thanks, this is interesting.

Fair chance Blizzard expected he had at least made a copy. Their being so generous with gifts and inviting him to speak with him personally seems to me a desperate effort to generate even more loyalty in him, which is actually really smart. It's their best chance for very little money and effort to prevent this source code to circulate on the internet.

with a vast reduction in complexity

That is very optimistic looking at the current state of client side development with it's ever changing Javascript, Babel, Typescript, whatever script, Webpack, with HMR?, React or Vue? Angular? Flux? Redux? Isomorphic? Linters? Testing? CI? CSS/???SS or inline?, some NPM modules maybe?, and so on.. Sorry for me being a bit more pessimistic here.

The bad news is they're targeting students. Who wants to see his children being locked into MS Windows software by school? Besides, we just found out Windows 10 has almost complete control over your system and calls home, now sending your kids private data as a bonus!

I would never accept my kids using a device like this on school. Schools are just ignorant and stupid if they make a deal for these laptops with MS. Schools should go for linux and open source, more educational as well.

10x developer is just a metaphore, not based on some mathematical model. For me it relates to the difference between an average singer in an average band and Prince or Whitney Houston for example.

10x is a metaphor. I believe we also have 2x, 3x, 8x dev's, it's a very relative factor. But it sure is an illusion to think that 10 average guitarists together will produce better results than hiring Paco de Lucia or Jimi Hendrix if you like.

It all depends on the job to be done and being the right fit. But some people have this talent and skill to make the right decisions split second, over and over again.

I definitely prefer one 6x dev over 6 average developers that are creating a horrible spaghetti of bad ideas and poor decisions, not talking about all the meetings they need to align and try to fix the mess they continuously create themselves.

Software Development is often about human factors as much as it is the code.

Totally true that. But the title almost suggests you can build a winning team out of a random bunch of average developers.

Although the best developer is an illusion as it doesn't exist as such, just 'building teams' doesn't really say much to me too. I've seen very terrible teams that should have been replaced with just 1 good developer..

Personally I prefer to hire the best fit for the job, whether he or she will be part of a team or not.

cool project, but why not spelphuckar.cum?

I was interested, until I saw the way too minimalistic demo on the homepage. If you call it a DAW with VST support and so, than just a demo of a piano piece with a huge piano roll doesn't really impress.

I don't want to be too negative as I really like the idea. But at first sight this is by far no match at all with the great DAW's out there. You can say they are bloated, but no one says you need to use all the features that are available. With most DAW's you can make a similar demo with ease.

Once you get the hang of promises,

.then( you realize it's just a callback..

Not only do you get a big performance boost,

Depends on the size of your data. AFAIK handling immutable data has a performance penalty on smaller datasets. Before I go immutable I first assess whether I really need it.