Because It's Not Fun Enough: why languages fail
bytecode.news
Because It's Not Fun Enough: why languages fail
1–10 of 141 posts
Re: Because It's Not Fun Enough: why languages fail
#2Re: Because It's Not Fun Enough: why languages fail
#3This entire essay could be about AI adoption as well. Some programmers love to program, and while AI is great at producing the code, it doesn’t really viscerally appeal if one loves coding itself.
Re: Because It's Not Fun Enough: why languages fail
#4> For the person who only wants the notes, the sampler wins the job outright, completely. It will never play the wrong thing or at the wrong moment. For the person playing, it fails, because driving it costs more than playing, and it never touches the art at all. This entire essay could be about AI adoption as well. Some programmers love to program, and while AI is great at producing the code, it doesn’t really visce…
Re: Because It's Not Fun Enough: why languages fail
#5Re: Because It's Not Fun Enough: why languages fail
#6Bust: Python
Re: Because It's Not Fun Enough: why languages fail
#7Boom: JavaScript Bust: Python
Re: Because It's Not Fun Enough: why languages fail
#81) Objective-C is 40 years old.
2) Objective-C was used to create NeXTSTEP and by extension Mac OS X and iOS.
3) Objective-C is no more "awkward" than any other programming language. I actually prefer its verbosity to Swift's terseness.
4) Although Swift did eventually become more popular, the claim about Objective-C that "the moment Swift existed, it evaporated" is not only false but a gross exaggeration.
Re: Because It's Not Fun Enough: why languages fail
#9Re: Because It's Not Fun Enough: why languages fail
#10Boom: JavaScript Bust: Python
If anything, the time of the ubiquitous JS might be over when anyone can generate native UI without electron.