I suppose if people started writing lots of code that crashed on error in Rust some enterprising developer might improve the function to always return a non-error value and set it to ‘*’ in error cases.
Does anyone know why musl does this? Are they the only C library that behaves this way?
For a C library that famously tries to adhere to POSIX as much as possible, this seems like a crazy choice. From POSIX standard:
Upon successful completion, crypt() shall return a pointer to the encoded string. The first two bytes of the returned value shall be those of the salt argument. Otherwise, it shall return a null pointer and set errno to indicate the error.
https://pubs.opengroup.org/onlinepubs/9699919799/functions/c...
To the extent that systems that are configured in the vulnerable manner exist in the wild, I’m surprised they weren’t exploited years ago by trivial ssh bots.
P.S. Wow, I’m reminded of just how awful traditional UNIX-y C APIs and code are.
P.P.S. The musl code in question is nuts. The API it implements is awful. Seriously, here’s the manpage:
https://man.archlinux.org/man/crypt.3.en
You can’t call this function correctly. sshd’s “fix” is basically to assume that a too-short return is an error return instead of a success return.
PAM is also awful, but this is worse.
I suppose if people started writing lots of code that crashed on error in Rust some enterprising developer might improve the function to always return a non-error value and set it to ‘*’ in error cases.
Does anyone know why musl does this? Are they the only C library that behaves this way?
For a C library that famously tries to adhere to POSIX as much as possible, this seems like a crazy choice. From POSIX standard:
Upon successful completion, crypt() shall return a pointer to the encoded string. The first two bytes of the returned value shall be those of the salt argument. Otherwise, it shall return a null pointer and set errno to indicate the error.
https://pubs.opengroup.org/onlinepubs/9699919799/functions/c...
- Quoted phrase in the opening sentence
- Opening quote: “[Common] Lisp curse”
Other than that, the Common Lisp ecosystem is doing well thank you very much. Many contributors to SBCL, regular contributions to the important ecosystem libraries, vivid projects (Lem), new editors (mine) and plugins (OLIVE), some companies picking Lisp and somehow supporting the ecosystem (hosting conferences, contracting implementors). https://github.com/CodyReichert/awesome-cl/ · https://github.com/azzamsa/awesome-lisp-companies/ And yes, new vibe-coded projects too. Some are useful (ICL, cl-tuition…), some reinventing the wheel (badly) went nowhere. For some, we'll see.
- Ordinary term used more than once in the same comment
- “strange” appears 2 times
EDIT: after reviewing other comments in this thread, I can see how my post here wasn't received well by some. It looks like some people are questioning the trust put into Graphene. I definitely am not. When I said "strange partnership" here, that's not what I meant at all. I think Graphene is operating in a very hostile ecosystem and the more doors Graphene can open for their platform to reach people, the better. The "strange" part of the equation was more aimed at Motorola (and Google) for allowing privacy intrusions to happen and even encouraging it in some ways (Gemini), yet actively supporting a project that would counter it. Maybe I should have used the word "funny" instead of "strange".
- Quoted phrase in the opening sentence
- Opening quote: “starting MSRP of $1,599.”
No doubt it's a way WAY better device, really, but I don't see where I would actually need that. I happily toss the one I have around and don't even care if it gets stolen or lost one day, different preference.
> This is the only yt-dlp wrapper that allowed me to properly maintain the Playlist structure to any extent
I have the same requirement and it's possible to do it with the default yt-dlp:
yt-dlp --embed-metadata --parse-metadata "playlist_index:%(track_number)s" "PLAYLIST_URL"
- Quoted phrase in the opening sentence
- Opening quote: “Keep this on the down-low!”
- Quoted phrase in the opening sentence
- Opening quote: “15 unavailable videos are hidden”
There's videos from ~15 years ago that I consider gone for good - lost to the great copyright apocalypse - having been unable to find them anywhere on the today's internet.
Yes, terrestrial light pollution has been the number one problem since we invented electric lights, but satellites and terrestrial light pollution are both separate problems with different effects and different coverage. E.g. even though light pollution is much more harmful, you can escape it with a short drive, even if you live in a densely populated region. You can't escape the strings of satellites.
Separately: "Shortly after sunset" is a downplay. It can be hours. But in any case, it's the time when the vast majority of stargazers are looking at the stars (with their eyes).
Satellites have the same awkward sociopolitical energy infecting them as all tech does nowadays. But remember: There is absolutely nothing wrong with being upset about the effect of these satellites, just like there is absolutely nothing wrong with being upset about the effect of electric lights. You can certainly get a lot of mileage out of weighing this against the consequences of having much fewer satellites, and that's exactly where all the argument should be occupied. That they affect the night sky, which reasonably annoys many people, is just a fact.
Even if I were to be as charitable as possible to your interpretation, "mendacious" is way too strong a word, and implies an unreasonable bitterness.
This is less an "image of our satellite-choked night skies" and more "a completely mendacious image produced using Photoshop".
Your example would look like this:
export component Hello inherits Rectangle {
in property <string> text: "World";
width: 500px; height: 500px;
background: #505050;
border-width: 1px; border-color: blue;
drop-shadow-blur: 15px; drop-shadow-color: #0008;
VerticalLayout {
alignment: center; spacing: 12px;
Text { text: "Hello, \{root.text}!"; font-size: 20px; color: white; horizontal-alignment: center; }
HorizontalLayout {
alignment: center; spacing: 8px;
for c in [#f00, #0f0, #00f, #ff0, #000, #fff]: Rectangle { width: 32px; height: 32px; background: c; }
}
}
}
More on why we chose a DSL vs code in Rust: https://slint.dev/blog/domain-specific-language-vs-imperativ...Things are crazy now. Our TVs snapshot the stuff we watch; our telephones, watches, and TVs are constantly listening what we say; our PCs have undocumented "remote administration" devices that we can't opt-out; every internet service out there is stealing every data that it physically can and selling it to a long list of organizations, including some military ones...
Recently, thanks to AI being this cheap and accessible, the amount of shitty PRs quadrupled if not more. And the worst part? Agent doesn't care about the checklist at all and re-writing the PR body with bunch of nonsense that we maintainers need to read, understand, and evaluate. I started keeping the score for the most shittiest PR based on how soon after the first commit made they open the PR. It was 11h, then 10h, and now it is 6h. How on earth a 6h old repository with zero user is considered "awesome" I don't know, but people should stop prompting their agents to create 10s of these PRs every day.
Yes, there's always an alternative: stop maintaining these lists. I don't think it's a viable option either. Sometimes you start using a new piece of tech and want to have access to somewhat curated list of resources that might speed up your understanding. There's still a bit of value to keep them alive and it's dying out bit by bit (literally) every time someone mass-creates these spammy PRs.
Thanks for reading my unsolicited rant.
- Quoted phrase in the opening sentence
- Opening quote: “awesome”
I would rather hear from users of software and their opinions, otherwise I can't take seriously something ostensibly curated for quality. In my experience such lists serve better as a way to discover new projects using eg. some framework you're interested in, if they're maintained (which is still valuable).
- Quoted phrase in the opening sentence
- Opening quote: “figure it out”
If you were lucky, there was a tutorial how to do X. But requires tool Y. Where do you get Y? Here it is on some apache indexed site! Oh, I just installed Sp0rk3h. Well, time to reformat and reinstall Windows XP. Good thing I partitioned my 40gB HDD
The learning curve for Photoshop 7, when there are 0 resources was pretty tough. I remember how proud I was when I figured out how to make an animated gif. Hammer editor (Was it called Hammer? to make maps for Half-Life engine games like Counter-Strike), There was an editor for creating an archive of images. was it a .WAD archive?
That kind of self-directed learning without hand-holding, I think, is not a bad thing
They restricted wage growth too much for too long under Intel (despite being the only growing business unit), so the people with the valuable experience moved elsewhere. The Agilex line-up finally looks to be in the place it should have been 3 years ago, and it seems like they brought in a good marketing team following the Silverlake acquisition, but they still fall in this weird middle-ground now selling "performance-per-watt", which is a hard sell when most engineers optimise for the extremes. If I'm just need a bridge or some glue-logic, I don't need a device which will singe my thumbprints off while doing that. Generally, if you want better performance, AMD does an excellent job, or if you need low power consumption, Lattice is like 4 or 5x lower or more with just enough fmax and IO to be dangerous. If you look read Lattice's shareholder briefings, they're running away with the low/mid-range devices up to ~500k LUTs, and AMD is dominating anything 1M+. I couldn't help but laugh the other day when I saw an Intel reference design with a Lattice MachXO5-NX on it. Look at pretty much any datacentre rack now, and you'll spot 4-64 Lattice devices, when it used to be MAX10s top to bottom. Everything else is swept up by AMD.
For Altera, Agilex 9 (ADC and DAC converters integrated with an SoC FPGA) is probably their most interesting device, but that customer base is limited - basically comms and maybe radar with some weird and wonderful optical or quantum compute applications. I've heard friends of mine in the industry say very good things about it, but RF is not my strength so I can't comment.
In all honesty, they've got an insane fight on their hands to regain the market share. They canned their low end road-map when Sandra Riviera came in (as a classic Intel VP would do) and put all their eggs in the Agilex 7 basket for a long time. They've got Agilex 5 now (and Agilex 3, which is just the bottom SKUs of 5 with it painted over by marketing to fill the gap), which is great for vision applications, but only because they had a fantastic video and vision IP team who last I heard have left for ARM.
I hope they pull it back, as I loved the people there and it had a great culture, but it's been awfully mismanaged for a while and I question how easy it will be to pull it back considering the monopolies and duopolies that are appearing in the semi industry right now.
Yes, openbsd has not had a torrent of bugs found, but I would say that the vastly bigger reasons for that are: 1) orders of magnitude people care about burning tokens and money to find the bugs in an OS almost nobody uses, and 2) it's simply much smaller. Can't have Bluetooth bugs if you don't have a Bluetooth stack.
I've pointed LLMs at obsd stuff, and even the simplest code, e.g. cat & find, had bugs and buffer overflows.
OpenBSD also has a poor patch tracking system, since they're still on CVS. A patch has an extremely good chance of just falling through the cracks. Security or not.
So no. Nobody can write safe C. Not hobbyists, and not "those evil corporations".
I've been working with a LoRa chip called the LR2021. I plugged a dev board into my computer and told Claude to reverse engineer it. He dissected it with a speed and level of efficiency I couldn't believe. Within a few hours, Claude was writing custom patches for a completely opaque patch RAM area meant only for the manufacture. I wrote about it here: https://beala.substack.com/p/your-node-doesnt-need-a-microco...
- Quoted phrase in the opening sentence
- Opening quote: “die”
Claude Fable is now good enough that I should be using it. The latest Claude version is said to be comparable to a mid-career graphics programmer, which is about what I need. Six months ago it wasn't good enough to use for such work, and probably would have made a hash of my code. There's been progress.
But Anthropic's business practices are scary. They have a reputation for cancelling accounts for random reasons, offer rather bad terms, and have no customer support. I have a strong aversion to services with a reputation for cancelling services arbitrarily. They will apparently cancel based on their system's guesses as to what you're working on. Sometimes they guess wrong. What I'm doing (metaverse clients) is so far out of the mainstream they may guess wrong.
I'm currently stalled signing up for Claude because their verification email system can't get to my inbox. (Some problem with their using Constant Contact, a spam system, to send transactional emails to my own domain, which, long ago, I had blocked at the Constant Contact end. I think. The verification email never touches the inbound mail server.) It's very important to Anthropic that you sign up with the "right" email address, and it may not be possible to change it, so using some disposable address is not a good idea.
Suggestions?
I think the argument is pretty simple:
- Plastic is bad (environment, microplastics, etc) - We should minimize it
That doesn't necessitate a "all the way to zero or don't bother" logic, which what you're saying reads as.
Coffee pods machines have been an environmental nightmare, great to see a growing trend that addresses this.
A lot that I see have extremely cheap-looking fixtures and little to no decor, and unlike virtually any other store, they stock what they stock, which is generally the same as every other vape shop, and don't even bother to fill out the entire space if it would hold more merchandise.
I assume some are able to negotiate lower rents in exchange for short term leases while the store is technically still on the market for a long-term lease, similar to a pop up store. A lot that I've seen could be shut down, with all the merchandise and equipment loaded into a UHaul, within a few hours if necessary.
Nail salons are similar. They really should have custom ventilation systems since they're working with paints and solvents and glues and nail drills/lathes, but this seems to not be enforced since they're seen as girly little spas rather than industrial workshops and are often staffed by poor immigrants.
Central planning is the status quo. That's essentially what zoning rules are, and why everything is such a mess. You want to open a shop and live above it? No, sorry, not zoned for residential; banned. Operate the shop out of your house instead? Haha, banned. What if your shop really doesn't need very much space at all, so something the size of a closet would do as long as it's in the right location? Nope, minimum unit sizes or similar, prohibited by law. And so on.
If they want to stop doing this that would be great, but if they're not going to stop doing it then having the rules be things like "no chains" instead of "no small units" would certainly be an improvement.
A race to the bottom, but I wouldn’t blame Amazon. Large multinational chains were hollowing out high streets and making them less pleasant before online shopping.
As another comment said, councils and government should treat high streets more like public commons, prioritising independent businesses and making places distinctive.
What frustrates me is that even prosperous areas with new developments rarely make space for small businesses. Instead, we get “private equity” chain.
Ugh, one I saw recently was Bristol University’s new campus by Temple Meads. The wall between the campus and station could have been lined with small, affordable units for independent and student-run businesses. Would love to browse a few interesting shops or grab a decent sandwich before catching a late train. 23m for a new entrance but where are the opportunities. (This is based off the media announcements, not walked through there yet)
- Quoted phrase in the opening sentence
- Opening quote: “you’re not the target demographic”
- Opening sentence uses a quote to challenge or distance a term
- Opening sentence challenges the term “you’re not the target demographic”
- Quoted phrase in the opening sentence
- Opening quote: “aesthetic”
It is entirely possible to prompt engineer away from that style, but that requires effort and knowledge that said average person does not have, so it's stuck in a feedback loop.
- Quoted phrase in the opening sentence
- Opening quote: “AI look”
Like, I'm not even an artist, so I'm sure there's a million things I'm missing, but it's just so upsetting to look at. There's weird random reflections on things that shouldn't have reflections, the coloured light absolutely doesn't actually track through the stained glass onto any surface that makes any sense, light is coming from every which way, it's just... gross to look at for anything more than a quarter of a second.
And this is what they're using to hype people up for it. /shrug
- Ordinary term used more than once in the same comment
- “perfect” appears 2 times
Godel’s theorem says that unprovable true statements exist. Fortunately there is a vast set of provable true statements that are quite useful in real life.
Similarly, the halting problem is that you can’t write a program that always determines whether absolutely any program you give it will halt. But in real life compilers can still detect infinite loops in your code unless you try really hard to fool them.
In practical terms a software system can never be “perfect”, because first you have to define “perfect” (i.e., specify correct behavior in every possible state), which is practically impossible, and even if you manage that, the hardware has to implement the software abstraction perfectly, and that never happens. (See prefetch attacks, cache timing attacks, supply glitch attacks, rowhammer, etc.)
The security issues come about when someone finds where you failed to specify desired behavior, or (at any level) your system failed to implement it in some circumstance. No strange loop required.
I remember reading Godel Escher Bach back in the day, and there is the parable of the record player between the tortoise and the rabbit. And the tortoise keeps building more and more secure record players that the rabbit keeps finding ways to break.
GEB then goes on to teach you that, no, in fact, you cannot have a perfectly secure system. Not just practically or economically, but even in theory, all systems are fundamentally breakable. GEB, after a lot of chapters (what a doorstop!) ties that parable into Godel's Incompleteness Theorem, and essentially proves that no, you can't make unbreakable things, as a fundamental point of logic.
So, when I look at all this, I see that yes, there is an economics point of view here, that fixing code is just expensive, like making a less and less breakable record player. And that AIs push that breaking and economics point much further along than what we have had.
But then I also see a lot of comments here that seem (to me) to be arguing that there is an unbreakable code out there.
Am I reading this right? Is there such a thing as 'perfect' code? Or is my outdated reading of GEB still valid or not?
[0]Note, I'm not a CS person, more a biophysics person.
Namely:
> The only way to do that is to make your code provable.
Proofs are a mathematical concept. They only work in the abstract world of mathematics where everything is perfectly logical.
Engineering exists in the real world. The physical realm where our mathematics are only imperfect models of what actually exists. Removing bugs through physical engineering requires persistent trial and error until you have found all the places where our mathematical models don't adequately represent the real world.
It's the same in software engineering, which involves cobbling together a myriad of systems not all designed to talk to each other and massive, ever changing codebases where perfect knowledge is impossible.
So yes, we should be trying to engineer bug free code. But that's really more a matter of changing our resource allocation, spending more time and money on QA and doing away with mottos like "Move fast and break things". It's a cultural shift and will only come when the bosses -- the venture capitalists who ultimately control our industry -- are held accountable when things break, and given strong incentives to ensure they don't break.
- Quoted phrase in the opening sentence
- Opening quote: “enterprisey”
Oftentimes there are two broad ways to fix a gap in the logic. You can eliminate the source of it, which often involves refactoring but tends to result in less code and cleaner, more comprehensible logic. Or you can leave the gap there, but attempt to render it safe by adding extra logic to detect and handle the error condition. This reduces changes to existing code, but makes the overall system more complicated.
You can’t just indiscriminately favor one approach. Which one of those is best depends on the situation. The deciding factor is often something like a time constraint that you can’t know just by reading the code. You might need to talk to your team before deciding.
But LLMs don’t do that. They always choose option B: slap a bandage on it. Keep on adding more epicycles. In the 2000s we learned that, over time, always choosing this approach inexorably leads to codebases that are brittle, bloated and expensive to maintain.
So the problem, from my perspective, isn’t that we shouldn’t be coding defensively. It’s that LLMs encourage us to do it in a way that we’ve already learned is unsustainable.
> -- Donald Knuth (if I recall that exact quote correctly)
Just because you have proven the correctness of your code, that does not mean that it is infallible. Especially -- as a lot of HN users point out -- there's intricate complexity that is likely to cause erroneous behavior if several interfaces/complexities get combined. And those might be caused, for example by a 'user' setting the driver to 'db.backend.sqlite' instead of 'db.backend.sqlite3'; and then you have suddenly an unexpected configuration.
- Quoted phrase in the opening sentence
- Opening quote: “data”
The only way to do that is to make your code provable. That again is only realistically doable using AI.
In the process, people will have to turn the pretense of "software engineering" into reality, making the engineering part explicit.
That only works when humans actually understand what they're doing.
But explaining that openly, as is your duty, means surfacing something which could be read as 'bad work' by a non-technical manager unable to grasp the complexity. So in low-trust teams it very quickly becomes a game of brinkmanship, or a prisoner's dilemma for technical diligence
It totally feels like the former if you watch it find and fix vulnerabilities or other debt-tasks one after another.
But only so many of these "technical debt" issue are little off-by-one errors that get remedied by a surgically narrow patch.
Many enough require some kind of restructuring or redevelopment of their own and it's going to take time to figure out if AI faces the same dilemma as human developers: where each non-trivial change carries the risk of some new issue, ad infinitum.
If that happens to be the case, and AI isn't able to magically produce perfect software in finite time, then what's really happened is that the threat of hostile AI exploiting our technical debt will force us to always be burning and churning code just to remain a moving target.
It's another "we'll see" thing for now, I think.
First, I am not a PHP fan, but I will absolutely stick up for the "its good now".
Yes, absolutely no debate the old PHP 4.x/5.x was shocking. However to give PHP their due, they absolutely did make serious efforts in 7.x/8.x. They deserve due recognition for that.
Unfortunately lots of people – I'm guessing you're one of them – still have battle-scars from 4.x/5.x and they think (incorrectly) that 7.x/8.x is "more of the same".
Second "joke language", well, cast your mind back to what else was available at the time... ColdFusion, CGI, ASPX ... it was not exactly a beautiful world back then.
Sure, to borrow your terminology, the Java fans will be along soon to tell us all how awesome Java is for the web. But many of us still bear battle-scars of the horrors of Java stacktraces, messing around with incomprehensible XML config files, Java's penchant for eating RAM for breakfast, and generally trying to figure out why the hell Tomcat is not working (again !).
Everybody in the industry knows that we've been building on quicksand. Moore's law meant that we could just sacrifice performance and add a dozen layer on top of technology from the 90s (if not older) and keep the thing chugging along.
Look at the PHP situation:
- HTTP is an old and quirky protocol with a lot of surface open for attackers that are rarely useful nowadays and might be better left off to higher layers. But of course, we can't break compat, so everybody still implements all the naughty parts, just in case.
- PHP was a joke language from the start, we were making fun of it in the early 2000s, the fact that over 20 years later it still powers a huge chunk of the web is enough to demonstrate that we're not serious people. Cue the PHP fans telling me that "it's good now". Maybe, I don't really care, the effort that went into making it good should have gone into ditching PHP for a better language 20 years ago. The bandaid mentality is what got us in this situation.
- And of course to add insult to injury, PHP, this security-critical language, is still implemented in garbo C using things like setjmp/longjmp. Just to make sure to absolutely maximize the damage if a vuln is discovered, I suppose. Brilliant.
- Oh and all of this is still running overwhelmingly on top of x86 which is its own bag of legacy garbage. "No but you don't get it, modern CPUs are really more like RISC CPUs, the RISC ISA is translated internally" yeah exactly that's my point let's stop doing things like that.
We're a clown industry. We only made it this far because, usually, buggy code doesn't kill people and we can iterate and patch things quickly. We never had to do things correctly, we could flourish with abysmal levels of quality acceptance. This may not be true anymore.
Of course the reason things are done this way is generally to maintain backward compatibility and make transition easier. At least now that we have LLMs this excuse will hopefully vanish: porting even huge codebases to a new language/framework, something that was a tremendous undertaking mere months ago, is now vastly easier and faster. We can leave the 1990s behind us.
- Quoted phrase in the opening sentence
- Opening quote: “She picked up what she thought was a stray dog that she thought was malnourished,”
Doesn't help that pet dogs spend much of their time laying down, with perhaps a couple brief respites in the form of a gentle walk.
They gain weight.
A healthy dog can often look malnourished to pet owners.
- Quoted phrase in the opening sentence
- Opening quote: “AI planned my vacation”
"You can call an Uber with a voice command"
"You can ask alexa to buy you things"
"Your AI will order food for you"
Seem like magical ideas that will remove friction and increase sales. Except that regular people compare 13 different options to pick the cheapest one. No one wants to see food appear on their doorstep followed by a bill they cannot pay.
My budget app, for example: It’s not easier for me to ask the AI bot “show me all my transactions from McDonald’s” than it is to click on the search bar/payee filter and type “McDonald’s.”
But if I use the AI bot, I’m burning tokens.
- Quoted phrase in the opening sentence
- Opening quote: “buy me more paper towels”
I'm no expert but even I've read that "Works at the White House" is bigger than the executive residence and oval office, including the West Wing and the big office building that's directly connected to it by basement walkways. The National Security Council maintains 24-hour watch operations in the Situation Room (which is more a 'complex' than 'room'), while regional desk officers routinely work late evenings to overlap with morning business hours in Europe and Asia.
I asked Gemini if my recollection was correct and got: "The EOP network (managed by the EOP Office of Administration in coordination with Presidential Information Technology Community entities like the White House Communications Agency) operates as a single campus enterprise network. Its high-speed backbone links the West Wing, the EEOB, the East Wing, and nearby administrative facilities such as the New Executive Office Building (NEOB) on 17th Street."
So, definitely an issue that there's a device with some rogue malware installed but the total workforce across all shifts at the White House Complex is roughly between 2,500 and 4,000.
https://darknetdiaries.com/episode/172/
There's a transcript if you want to read, not listen. At the start, you'll be "hey! I gotta get me one!" and later you'll be like "burn it with fire!"
- Quoted phrase in the opening sentence
- Opening quote: “anonymization”
If there's anything there, monitor your network to figure out exactly what
Person buys a product, or downloads some software - that unknowing to them, was reaching out to a central server elsewhere to establish a network tunnel. And over that tunnel, the other server routes traffic onto that person's home network. Which can then of course go onto the internet, and it appears like the traffic originated from their home internet connection.
Other people rent access to this network. The goal being, you have surreptitious access to appear as any one of tens of thousands of home network IP addresses on the public internet. Bad guys can use this to rotate through many different IP addresses when their access gets blocked because of malicious (or benign but unwanted) behavior on the internet. Residential IP addresses are more 'valuable' because they don't have the negative connotation that datacentre and commercial IPs can have, and they can be spread geographically or across many ISPs.
A very common way for people being a part of these residential proxy networks is by buying dodgy streaming boxes, and also installing shady apps on TV app marketplaces.
- Quoted phrase in the opening sentence
- Opening quote: “Simple Object Access Protocol”
- Quoted phrase in the opening sentence
- Opening quote: “JavaScript Object Notation (JSON) is a simple data interchange format [...]”
- Opening sentence uses a quote to challenge or distance a term
- Opening sentence challenges the term “JavaScript Object Notation (JSON) is a simple data interchange format [...]”
Clearly it isn't, otherwise every language would have sorted it out by... a long time ago.
- Quoted phrase in the opening sentence
- Opening quote: “small transfers very quickly”
- Quoted phrase in the opening sentence
- Opening quote: “edgy-ness”
No AI, no leet code, just old fashioned gauging someone's experience and communication skills.
And another in Dresden: https://www.youtube.com/watch?v=cQUpQZAeA3w https://www.diesachsen.de/en/politics/a-zebra-crossing-in-dr... "In the summer of 2025, unknown individuals painted a crosswalk on the roadway along the busy street in Neustadt to provide safe access to the Heinrich Schütz Conservatory. The city promptly blocked off the crossing with warning cones [...] stating that unauthorized crosswalks constitute not only property damage but also a dangerous interference with traffic. Furthermore, traffic signs installed without authorization constitute an administrative offense under the Road Traffic Code."
In Los Angeles https://www.latimes.com/california/story/2026-10-16/risking-... "Risking arrest, he paints illicit crosswalks across L.A. ‘We can’t wait any longer’" (initially repainting faded crosswalks, rather than creating new ones)
And an example in Saskatoon, visible only in the 2015 street view image https://maps.app.goo.gl/3zWAkjtSEATswcWm8
They made up the term jaywalking by combining "walking" with the term "jay" which was a slang term for a country bumpkin or idiot from out of town. They hired actors to spread the slur to refer to those out of towners that don't know how to "properly" behave around streets in a modern city. They even paid Boy Scouts to hand out warning cards and staged mock funerals
As to the time investment:
> He spent more than three months preparing, researching the color and shape of the signs, mixing his own custom paint to get the colors just right, and applying a bit of faux patina to finish it off. Ankrom even spent time tracking down the button-shaped reflectors used on other legitimate signs and convincing the supplier to give him some. Once he was satisfied that it looked authentic, he came up with a plan to install it.
---
Caltrans has 15,000 miles of state highways that they have signage for. A single sign may only get reviewed once a decade because of that.
Doing single things in isolation is "easy" without going through the required public comments and such. Maintaining it for the entire state is much more challenging.
Vehicular cycling techniques can help in situations where there is no bicycle infrastructure, but they are not safer than good bicycle infrastructure.
- Ordinary term used more than once in the same comment
- “5 North” appears 2 times
> And then…nothing. Caltrans didn’t notice. Passing motorists were thrilled but figured the improvement had taken place at the direction of Caltrans. It wasn’t until Ankrom leaked his actions to the press that the true story was known.
> The original sign with Ankrom’s artwork remained until 2009 when the whole thing was replaced by Caltrans. The paint had faded, but the message remained with a lasting impact. The replacement sign erected by the Department of Transportation proudly sports the 5 North placard exactly where Ankrom had put it nearly a decade prior, and it remains there to this day to help motorists that would otherwise be just as confused as he was.
And an update from 2023:
> In 2001, artist Richard Ankrom posted a "5 North" sign on the 110 N. in DTLA to alert drivers to get in the left lane for the 5 turnoff. His work was so impeccable (and helpful), Caltrans at first didn't notice, then allowed it to stay. "5 North" is now part of permanent signage.
The Swiss police under prosecutor Walther Cimino proceeded to investigate as if they were a crime syndicate, gathering forensics but also identifying 96 sympathizers and putting them under heavy surveillance, which included requesting total records from their banks, employers, phone companies, email providers (Google through the US DoJ), and even CCTV and purchases from their local supermarket.
I'm afraid of the possibility that what used to be "grassroots civil disobedience" will now be labeled "eco-terrorism" and prosecuted accordingly.
Drivers and pedestrians hate each other too. Everyone gripes about any minor impediment to their own travel, particularly other modalities, but also their own. I mean, drivers universally complain about being "stuck in traffic", but they are traffic.
> We found that LEDs attracted significantly fewer insects than other light sources, but found no significant difference in attraction between the “cool” and “warm white” LEDs.
Also, not sure about white bulbs, but those color-configurable spotlights definitely emit UV at least when set to anything near blue/purple. They cause certain things to glow. Probably white is doing it too but it's harder to see.
- Quoted phrase in the opening sentence
- Opening quote: “This is a notice, not an argument. The argument comes later.”
- Opening sentence uses a quote to challenge or distance a term
- Opening sentence challenges the term “This is a notice, not an argument. The argument comes later.”
GAG
What a laughably insulated statement. An example from NZ - Janek Patel was murdered in 2022 while attempting to prevent the cash register at his corner store from being stolen.
The figure has been described as "a few dollars".
I asked "what the hell?" and he said "this is for me to use in case somebody talks shit about your father".
Upon some investigation, it turns out that the nicest guy in the world was actually living in my city because he was on the run for a murder he committed in another city many years back. The nicest guy in the world had an altercation with another patron at a bar, while drunk, broke a beer bootle on a table, stuck into the stomach of the other guy, and twisted left and right until internal organs started showing.
I did befriend a murderer once.
- Ordinary term used more than once in the same comment
- “frontier” appears 3 times
> Introducing Ripple-65B Preview, a Frontier Open-Weight Model
It's not "frontier", it's not "frontier" even in the category of open-weight models (though usually that phrasing would mean frontier over all, and also open weight)... it's only "frontier" in the small sub-category of US made open-weight models.
- Quoted phrase in the opening sentence
- Opening quote: “SOTA”
You mean it's state of the art for this subset of benchmarks you're targeting? No? Well surely it's state of the art for models of a certain size category? Huh, what about models that are available for local inference? O, state of the art for open models of a certain size made in the US specifically. Uh. Neat!