@vlascik.bsky.social
do JSON:API people know that? because as far as I can tell, the query part is just as bad as it was 10 years ago.
July 8, 2025 at 7:44 PM
do JSON:API people know that? because as far as I can tell, the query part is just as bad as it was 10 years ago.
ok, thanks for the info.
March 14, 2025 at 3:53 AM
ok, thanks for the info.
are you sure? all I see on GH are changes to the wire format, but nothing for it to be turned into the vanilla JS...
March 13, 2025 at 6:34 AM
are you sure? all I see on GH are changes to the wire format, but nothing for it to be turned into the vanilla JS...
and yes, the invokable wire format might help to reduce the extra processing needed, but there still will be a non-zero amount of it. I suspect it's just another dead end, or just maybe a minor improvement.
the end-result should be just a minimalistic vanilla js program.
the end-result should be just a minimalistic vanilla js program.
March 13, 2025 at 3:31 AM
and yes, the invokable wire format might help to reduce the extra processing needed, but there still will be a non-zero amount of it. I suspect it's just another dead end, or just maybe a minor improvement.
the end-result should be just a minimalistic vanilla js program.
the end-result should be just a minimalistic vanilla js program.
the only way to get to the vanilla's performance is to BE vannila.
Ember should turn the wire format into vanilla js code on first component use and only execute that from then on. don't get why it's not done that way.
Ember should turn the wire format into vanilla js code on first component use and only execute that from then on. don't get why it's not done that way.
March 13, 2025 at 3:31 AM
the only way to get to the vanilla's performance is to BE vannila.
Ember should turn the wire format into vanilla js code on first component use and only execute that from then on. don't get why it's not done that way.
Ember should turn the wire format into vanilla js code on first component use and only execute that from then on. don't get why it's not done that way.
render time is just what happens after you call that browser's createElement, so of course that time will be the same across the frameworks.
ember's problem is in the excessive JS execution overhead, which doubles the total time spent on each element.
ember's problem is in the excessive JS execution overhead, which doubles the total time spent on each element.
March 13, 2025 at 3:31 AM
render time is just what happens after you call that browser's createElement, so of course that time will be the same across the frameworks.
ember's problem is in the excessive JS execution overhead, which doubles the total time spent on each element.
ember's problem is in the excessive JS execution overhead, which doubles the total time spent on each element.
this looks way differently than their official numbers at krausest.github.io/js-framework...
Interactive Results
krausest.github.io
March 12, 2025 at 7:35 AM
this looks way differently than their official numbers at krausest.github.io/js-framework...
Second, plenty of people (me included) will never buy a silver laptop, no matter what - so the environmental choice is not between a silver FW laptop and black FW laptop, but between black FW and black throw-away laptop.
So which is more environmentally friendly?
Their stance on this Is just nuts.
So which is more environmentally friendly?
Their stance on this Is just nuts.
February 27, 2025 at 6:09 PM
Second, plenty of people (me included) will never buy a silver laptop, no matter what - so the environmental choice is not between a silver FW laptop and black FW laptop, but between black FW and black throw-away laptop.
So which is more environmentally friendly?
Their stance on this Is just nuts.
So which is more environmentally friendly?
Their stance on this Is just nuts.
Chip-making is a very energy and rare material intensive process. Pretty dirty too.
February 27, 2025 at 6:09 PM
Chip-making is a very energy and rare material intensive process. Pretty dirty too.
oh they actually have a rationale for not doing that, anodizing/powder coating causing more pollution or something.
I seriously worry about companies run by people not seeing the flaws in that logic.
First of all, by the time the production gets to the anodizing part, the damage is already done.
I seriously worry about companies run by people not seeing the flaws in that logic.
First of all, by the time the production gets to the anodizing part, the damage is already done.
February 27, 2025 at 6:09 PM
oh they actually have a rationale for not doing that, anodizing/powder coating causing more pollution or something.
I seriously worry about companies run by people not seeing the flaws in that logic.
First of all, by the time the production gets to the anodizing part, the damage is already done.
I seriously worry about companies run by people not seeing the flaws in that logic.
First of all, by the time the production gets to the anodizing part, the damage is already done.
it all seems great until you realize it's been 5 years and they still haven't figured out...*checks notes*... the black laptop technology.
February 26, 2025 at 10:12 PM
it all seems great until you realize it's been 5 years and they still haven't figured out...*checks notes*... the black laptop technology.
well, today's html wysiwygs are awesome. in fact, they've been awesome for the last 8-10 years or so.
February 1, 2025 at 1:30 AM
well, today's html wysiwygs are awesome. in fact, they've been awesome for the last 8-10 years or so.
plenty of maintainers that won't fix breaking bugs because of simple laziness.
even with PRs ready. even after people beg them to do it, for years on end, wasting work of all the others that came before them completely.
bad OSS etiquette goes both ways.
do not make people write these comments.
even with PRs ready. even after people beg them to do it, for years on end, wasting work of all the others that came before them completely.
bad OSS etiquette goes both ways.
do not make people write these comments.
January 19, 2025 at 2:14 PM
plenty of maintainers that won't fix breaking bugs because of simple laziness.
even with PRs ready. even after people beg them to do it, for years on end, wasting work of all the others that came before them completely.
bad OSS etiquette goes both ways.
do not make people write these comments.
even with PRs ready. even after people beg them to do it, for years on end, wasting work of all the others that came before them completely.
bad OSS etiquette goes both ways.
do not make people write these comments.