The collapse of the JavaScript ecosystem
-
Apparently, as of about yesterday, the JavaScript ecosystem is no more. Goodnight, sweet prince, and may the angels...
...whoops.
-
it's measuring projects hosted on github i assume?
if so github has made some changes to its apis lately that are probably screwing with the tool. that's not the only site that integrates with github that's had issues.
-
I'm guessing GitHub, being all open-source-y, uses the Twitter and Facebook method of API updates, where they completely fuck over all users of the API by making random changes at weird times (Friday at 9:00 PM to guarantee the site will remain broken as long as possible!) then might mention, "oh hey we're going to be making some API changes" on their developer blog about 3 weeks after your emergency scramble to get shit working again.
-
What if they followed the MSDN closed sourcey methodology and just randomized the URLs for everything? Same effect, I guess.
-
Yes that's equivalent. Changing the URL of a help page is the same thing as breaking an API used by thousands of companies as their main source or revenue. Exactly the same thing.
There's no trolley icon on your post, so I assume you're actually posting this ridiculously stupid thing in good faith.
-
There's no trolley icon on your post, so I assume you're actually posting this ridiculously stupid thing in good faith.
Yes, of course. I agree with you that the URL changing stuff is ridiculously stupid.
-
Noooo, the API changes are worse, because all the URLs remain the same, they just serve up different JSON schemas.
If the Facebook and Twitters and GitHubs of the world changed the URLs when they changed the API, they'd run the risk of customers detecting and fixing the problem much more quickly. Much better when everything appears at a glance to work, but all your data becomes wrong.
-
Noooo, the API changes are worse, because all the URLs remain the same, they just serve up different JSON schemas.
I don't disagree with that.
-
Ok well I'm just going to add all the trolley icons you've been missing here:
-
No Swift in the list.
Doesn't seem like this page is updated very often.BTW, for extra lulz:
As suspected, languages come and go, but C is eternal.
-
If 2026 is your idea of eternity...
-
Just an off by 11 error!
-
Can one magnify the region around 2015.5? Maybe there are minor differences.
I say this because one of the possible causes of the longevity of C is due to its one-character name.
Btw, shouldn't one see where the white line of the most interesting language [None] crosses the gray lines?
-
off by 11
Only about 10. And if you look closer, about 9.8. Maybe 9.81, the gravitational acceleration in meters per second squared on Earth's surface reduced to mean sea level?
-
-
I say this because one of the possible causes of the longevity of C is due to its one-character name.
-
Okay, so that's not the cause.
http://blog.openhub.net/compare_languages/
@http://blog.openhub.net/compare_languages/ said:The most recent month is excluded because the Open Hub does not yet have complete information for it.
So due to the
weirdefficient representation of dates and times in C, 2025-08 is the current year and month in that language?Edit: Another interesting WYSIWTF behavior: While composing, a link in the quote source works just fine, but not when posted, and not in a subsequent edit either.
-
-
Edit: Another interesting WYSIWTF behavior: While composing, a link in the quote source works just fine, but not when posted, and not in a subsequent edit either.
Discofix (or as non-Discodevs would call it: ugly workaround):
[quote="<a href="https://en.wikipedia.org/wiki/Workaround">https://en.wikipedia.org/wiki/Workaround"</a>"] Typically they are considered brittle in that they will not respond well to further pressure from a system beyond the original design. [/quote]
yields:
[quote="https://en.wikipedia.org/wiki/Workaround""]
Typically they are considered brittle in that they will not respond well to further pressure from a system beyond the original design.
[/quote]By the way, those nested double quotes ( ) are not typo's...
-
Thanks. I hope I'll remember next time when I'll try something similar.
I wonder what will happen when a discodev will discothink about the nested quotes and will discofix them? Discoredesign of the thread?
-
I wonder what will happen when a discodev will discothink about the nested quotes and will discofix them? Discoredesign of the thread?
Don't worry. Jeff will ride to the rescue and discorevert the discofix. Unless it has round corners.
-
-
Commit #facd1467 : fixed all perf problems, also elevator has round corners now because Jeff
-
That actually doesn't look too hideous!
Off to meta.d?
-
-
Thanks. I hope I'll remember next time when I'll try something similar.
You could my post ;)
-
You could my post
I'll put the list where I note where to look for s on my list where to look when I want to discopost something as soon as I find this list. If I still remember when I'll have found my list of what to put on what list.
-
I'll put the list where I note where to look for s on my list where to look when I want to discopost something as soon as I find this list. If I still remember when I'll have found my list of what to put on what list.
Just put a Post-It on your screen, like regular people
-
Just put a Post-It on your screen, like regular people
Won't work. It's not a password…
-
Won't work. It's not a password…
Besides that, how should I know which one of the 4095 Post-Its to look at when I need it?
Filed under: Where did I put the note with the definition of "messie"?
-
Besides that, how should I know which one of the 4095 Post-Its to look at when I need it?
Don't you use different colors for different things?
-
Don't you use different colors for different things?
Of course, but I want to see you to tell #EEF2B1 from #EEF0AF when there are shadows in the office and differently colored areas on the screen behind the Post-Its.