countWSS
countWSS on Hacker News
Posted by
countWSS on Monday November 02, 2026 @10:30AM
from the self-post dept.
Last few days it was loading at snails pace.
Not 50x errors at every page. What is going on?
No outage is shown, just "Partially degraded performance"
Inspired by recent law proposal to tax dataflow per GB in France
Posted by
countWSS on Saturday October 31, 2026 @02:06AM
from the datacenterknowledge.com dept.
> surely the danger is much much lower
It depends on what chemicals the plastic reacts with. Its more of class of
pollutants like aromatic hydrocarbons, randomly forming when the plastic
reacts with something in environment, the paper has this explained:plastic
is "conditionally inert" material until it gets some electric charge.
Then it suddenly a chemical factory floor.
Its going to be next few decades version of asbestos x100,
The difference with asbestos is plastic is basically everywhere,
industrial plastic coatings in many "non-plastic" surface to reduce
wear or damage, since plastic resists acids/chemicals better "allegedly".
This paper is going to upend most dogmatic ideas on "non-reactive plastic" soon.
https://www.nature.com/articles/s41586-026-11141-y
i've tried various options, Firefox prefers ` for (let i = n; i--;) out[i] = a[i] * b[i] + 0.25;`
Its already at peak optimization so no form is significantly better.
IIRC in weird corner cases, JS code can outperform wasm/C/C++
because JIT optimizes with escape analysis/inlining.
>where it doesn't optimise to SIMD even when beyond obvious
What was that code?
Any "central payment system"(like e.g. obsession with Paypal)
is a single-point-of-failure vulnerability. Cash is decentralized
and independent of any technology failing.
people find this the hard way during electric blackouts,
that credit cards are useless without electricity, but somehow
still think "electronic payment" is worth completely switching over.
Yes, according to Socrates all writing is brainrot and libraries are essentially TikTok bingewatch.
It reduces tolerance for dealing with bullshit.
Who wants to start a stackoverflow humiliation ritual and breadcrumb following
random websites to find reliable stuff(90% of which is AI generated),
when prompting gets you directly to the answer?
Before that, the "Google rots your brain" articles prophesied the fall of humanity to
search engines: now its mark of intellect to able to manually
curate and search within websites for relevant info.
https://en.wikipedia.org/wiki/Is_Google_Making_Us_Stupid%3F
Actually, its just inertia and lack of reliable forum hosting,
the actual "killer app" that replaced volatile and unarchivable
chat content, but no one learned from it and people flocked to Discord,
which is even more hostile to archiving/scanning chat history.
The problem is scale. Trying to replace something
big like Reddit/Browser/some-huge-library requires
enormous resource investment which is inviting
the same forces that enshittified the original.
The original reddit was a link list with voting,
no comments/media/etc it was cheap, and as it grown
into social media giant with insane complexity, it became
much more expensive and slower to process(both on
client and server). But the users loved it, they
now don't need to host the video/image/comments elsewhere,
its all included inside the walled garden,
and reddit which was 100% links to outside resources
is now mostly self-contained media with
pictures, videos, blog posts(self.subreddit) being
most of content and hyperlinks to "outside" being
mostly mainstream "big websites" with social clout.
"Cheap-to-generate" mediocre content forces the floor expectation to rise, becoming
the "minimum", which raises expectations of "current mediocre" further.
Its largely invisible, slow process, where you can't gauge past
"floor-level" expectation for content, because it implicitly assumed the
'current year' standard is the norm(while its evolution of expectations).
In a few years, expectation for "mediocre slop" would likely include
stuff that considered top-level today, but has some minor deficiencies and
the "slop of years past" would be relegated to unusable/useless junk, like\
e.g. Stable Diffusion 1.5 images and GPT2 texts.
Wikipedia.org :270 cookies, 110MB used.
Never cleared or disabled any.
Posted by
countWSS on Tuesday August 04, 2026 @08:04AM
from the self-post dept.
Every single page is mostly sidebars, each has to be clicked
'hide' for every pageload(it does not save the state of sidebars!!) to reveal the article squeezed inside.
For the "full sidebars on" default, it requires either a 8k screen or 30% zoom to even see an article content.
Okay, lets imagine it get enforced and every project is
scanned for compliance, with some false positives
and inability to prevent people from sneaking in AI code.\
Do you agree with it now?
The copyright/Anti-ai angle is likely an excuse and they're running
out of money for hosting, hence errors and anti-scraping blocks.
Its completely absurd to think they somehow waited years to ban AI for copyright, while deleting
anything they deem as copyright infringing.
Looks like those vibe-powered opensource projects will mighrate
to somewhere else.
IKEA beds are underestimated: these flimsy POS planks and their
insertion is entire artform that was likely engineered to cause pain.
The idea here is they are huge, finicky and depend on precise positioning
in multiple areas, there is no "easy shortcut" for their structural integrity,
everything has to be perfectly assembled.
The neglected part here is latency, speed itself can be masked
by progress bars/animations, but having visible lag ruins the idea
of speed and users treat it as slow vs animated loading bar.
Ok, suppose you have a "trash/low quality" article and
"this article has been deleted", the article with some info
will win over the audience as they search for it. Like "Worse is Better", the quality
will improve over time and the "deleted article" will stay at 0 recognition.
An average internet user will not complain about the Wikipedia
article, they just switch to Grokipedia and whatever AI-generated content it has,
since they now have it.
Don't know why you get downvoted, but this is how AI-based projects
win over time: they don't randomly decide to delete valuable data.
Grokipedia might be trash in terms of its quality, but at least it
it doesn't have omnipresent moral busybodies loitering in to "purify" it from knowledge.
GCC already solved it:
https://gcc.gnu.org/onlinedocs/gcc/Vector-Extensions.html
The operations behave like C++ valarrays. Addition is defined as the addition of the corresponding elements of the operands. For example, in the code below, each of the 4 elements in a is added to the corresponding 4 elements in b and the resulting vector is stored in c.
Here and on reddit, AI debugging is viewed as some weird shallow
pattern-matching that obviously fails to spot real stuff and
overload the maintainers. Instead of getting to "spotless record"
of zero flaws, the people start rationalizing that "X is not a real bug"
and inventing justifications for their(obviously bad) code,
which is critique they can't accept from AI, only through human
debate that they can't close with a WONTFIX.
Once the bug is actually usable, the tune changes completely.
What is the 181M$ mysterious "Project Support" in the graph means?
Linux is labeled separately, so it cannot be the "Project".
IFUNC should be implemented by software itself,
like switching functions on runtime/compile checks.
Why bother having a slower, insecure version that is less
flexible than a function pointer? I have to agree with author.
Glibc is filled with even more nasty hacks ripe for new exploits.
That a media push to make "it more secure" i.e. closer to Chinese Internet ID.
Try to listen to music in language you don't understand.
The effects of having lyrics don't appear unless you focus on them to repeat the memory of song.
Of course instrumentals are better, but lyrics lift the mood by virtue of having some "virtual social context" simulation.
Sure, is there anyone nostalgic for debugging bash files by hand?
Any sense of grief for writing C++ template headers, with all boilerplate?
Hmm, does anyone like manually re-writing makefiles these days?
I suspect the enthusiasts of coding craft will struggle to maintain their wonder
after ~4h deep in any of these magical adventures, which surely
involve inventing ad-hoc duct tape and novel, never-before-seen algorithms.