yason

Owning your device (instead of the manufacturer, a set of unlisted governments, big software corporations, etc.) means no scanning.

Social media as it was born touched a novel point of contact that didn't quite exist before. It was a powerful shift from what we had before.

Social media allowed you to be in touch with people in a way that wasn't possible with phone calls, text messages, instant messaging, email, or domain-specific forums.

What I could do in Facebook in 2010 was stay "friends" with selected acquaintances such as old classmates with whom I never was in email terms, messaging terms, or any other terms except having known them in school (or at work or at a hobby or...) I could follow their life via their posts, and I could leave a comment, sometimes, without any expectation that we should ever talk, meet, chat, or become more than old classmates. I haven't sent email to anyone in my school that I didn't know outside of school, as a friend. I don't have their numbers and it would be awkward to even consider calling someone with whom we didn't necessarily even talk much in school. But it was perfectly okay to ask someone to be your friend on Facebook (like, Hey, I know you? and if he did remember he would accept) and follow their postings and maybe (re)kindle something with no pressure to grow it into anything more than that.

We had that. Now... we no longer do. Or we still have Facebook and we can send friend requests to old acquantainces that I'd like to follow but there's nothing to follow because they aren't posting and because Facebook wouldn't show me their posts. So we're back to the point where actually making contact with another person (on Facebook) basically requires sending them a message in Facebook. Which already goes beyond what's expected from an old acquantaince on Facebook.

I recall a site for classmates where you could register to your school years and see your classmates there. But that was before social media and there weren't any posts that you could comment. You could just see your classmates listed there, and one in ten might have written a few words in their profile. And that was classmates only, not ex-work colleagues or other people you've passed behind in your life. Facebook was really good at the time it became a thing.

We still have email, instant messaging, etc. but what's the platform today where I can keep in touch with people I'm not emailing or talking with? Is there one?

Emission controls are the best scapegoat for Deere and others to lock down systems as tight as possible for profit. They don't care about emissions, the farmers don't care about emissions, the emissions happen on a fscking large field out of nowhere instead of rush hour city traffic, and tractors usually run at high power which makes a cleaner combustion with less soot (but higher nox): all in all, the world doesn't become a better place because of farm equipment DPF/SCR filtering. But emissions are the perfect mandate for manufacturers to make it impossible for the owners to own the equipment.

The interesting part of this mostly bullshit is how it exposes a kind of reverse Goodhart's law scenario. When driving becomes less about attention to surroundings and focusing on driving and more about keeping the trivial beepers off, it changes the way people drive.

First, it will be less about motoring and driving a vehicle in a dynamic environment but focusing on pleasing the camera with your eyes. Back in the time my driving instructor said the eyes should move around all the time, every second to far, near, mirrors, side mirrors, etc.

Second option is that some people will just tune out of everything and I mean everything. When the car has too much to say they won't even look at or register at anything anymore. Blind spot warning is useful and so is engine high temperature warning or brake fault, but if you're constantly bombarded by ping pong bleep bing beeps who the fuck will care anymore?

Third, this will just prompt homebrew hacking to disable these things and basically de-digitize these complex systems. This will inevitably lead into a cat and mouse race between users who want to control and own their vehicle and manufacturers who are forced to keep controlling and owning the owner instead.

Obviously, if governments really cared about safety and not adding simple warnings to merely patch and train behaviour they would ban all attention-requiring context-specific user interfaces in cars that more than destroy all even theoretical safety gains from these beepers. It's illegal to look up your phone while driving but perfectly legal to wade in deep menus and panes via a touch panel while the car is beeping at you.

They should classify it as personal information, and you could share, sell, and publish it as much as you want.

If this continues long enough there will be plenty of 140-year-olds rocket-jumping through levels in TF...

biggest reason why air conditioning is not so widespread in Northern Europe as in the United States

It certainly is a transitional period where each summer more and more people realize that eventually something needs to be done, "maybe a/c next year" for many years until the year of installation finally comes.

In Northern Europe it certainly is still a rare occurrence that everything gets heated so warm that the air does no longer cool during the night and you can't cool down for the next day. Yes, we do get heat waves but they don't last very long. Yes, summers are mostly getting hotter but it's still nothing like in southern Europe. We might have several weeks of 25-28C with a lot of lakes and sea to dip into.

Admittedly it can be tormenting in city apartments where you might not have a place for A/C even if you wanted to, and where you might not have enough outside walls to effectively cross-ventilate. Further, the stone and pavement in a city absorb heat like a sponge which keeps the average a few degrees warmer than greenleaf areas across the hot season.

Yet I think maybe half-ish of households (or at least detached houses) already do have A/C. Installations have been steadily creeping up in the last 25 years. But those units aren't there because of their cooling capacity (which isn't necessarily always even used). Those are air-to-air heat pumps that keep the house warm in the winter, and can be used for cooling in the summer.

It's not that I don't agree, but lawyers will then ask you to define "buy" in such a way that

One fundamental thing would be to make it illegal to lawyer redefinitions of common words. If the sales of a game uses the word "buy" it should not be legal to redefine "buy" in that context to actually mean lump-sum lease or something.

I'm pretty sure the game studios wouldn't like me to buy their games if I were to amend the terms of sale with a clause in fine print that the term "pay" means "setting up a temporary IOU for which I reserve the right to have it resolved into nothing at my discretion". So, I'll pay later if I decide pay, maybe never. That's effectively what their "buy" means.

IRC's UI is horrible. (Like email.) No wonder people don't want to join it.

I consider it a feature that acts as a filter.

On a related note, does anyone know of a good (open source) golf simulator/game for Linux? Serious level gaming more than just entertainment, I'm thinking something like FlightGear of golf games.

Where do you store the indices? Blockchain!

Why bubbles happen? Because investors, out of greed, pour into corporations that burn their cash.

The internet was a bubble: you could make a web page and sell it for millions because next year it was going to be worth billions. And then internet grew up.

AI is technology that's still beginning to find its place to settle. It's far from mature and that's perfectly fine. We'll have reached a reasonable plateau once the technology and the related stack stops changing every month and instead develops incrementally and boringly over the span of few years. That's like internet in the 2008-2010, and many investors will have a collection of new burn marks by that time.

Not only financially there's an unsustainable push for AI by the zealots du jour who are more often than not managers rather than engineers. AI is championed most ruthlessly as a silver bullet revolution by people who least grasp the limitations of AI. It'll take some time to figure out the dreamed-up proceeds won't be there, and "then what?".

I predict that the real bottlenecks of development will re-emerge as soon as the limitations of AI will manifest out of the hype. They bottlenecks are human-based, in development processes and in human interactions. A large part of development is trying to understand what we want and what we need and you can't offload that to AI.

I can't understand the people who blindly believe any law is good just because. Stop, think. Is the law good? What's good about it? What's bad about it? Can it be abused? Then maybe it should be changed?

I think many people have an expectation that (all) laws are just and needed because... somehow they're the law.

In reality, laws can be unjust, unnecessary, biased, and completely arm-wrestled together by people strictly following an agency of their own. Other laws are put together by sheer ignorance and lack of thinking beyond mere good intentions. The first question shouldn't even be "is this law fair" but "was this law made fairly".

It creeps me that people treat laws as axioms whereas they're just polished and reinforced opinions. Sure, many laws we can agree on, and many others that don't agree on aren't worth changing, but you should always question the law and question where it came from before choosing to accept it.

I can see the same pattern with technology such as the various digital restrictions management (DRM) schemes.

My impression is that people who can work on stuff like that are the kind who just take the stuff in the world for granted. "This is how the world is, we need digital restrictions so now we need to implement them." "I don't have a say about whether DRM or remote attestation is standard business practice or not, it is just how it is."

This is akin to how two kinds of people respond to law. The first kind think "This is the law, we must follow it" and the other kind think "This law doesn't make sense, we must change it".

People who look at pedestrian traffic lights and cross when it's green vs. people who look at cars and cross when there are no cars coming. The first say you must follow traffic rules and the second kind say they wouldn't be alive if they looked at the green/red light of law instead of whether there are oncoming cars: a green doesn't mean it's safe to cross and a red doesn't mean you can't cross if only there are no cars.

I got my C64 in 1985. Obviously, I can revisit the graphics and sounds of that machine online now, via emulators and youtube videos. But one thing I always remember is the smell of warming circuit boards that oozed from the casing soon after you turned on the computer.

Anecdotally, the cassette player that came with the machine had a misconfigured tape head. Because there was no internet nobody knew why it didn't load most of the games I got with the machine. However, saving and loading programs did work. So, I started writing programs from the user manual and game listings from some programming books I found in the library, and saving them on my cassettes. Because the user manual covered not only some tutorial BASIC but also the machine's graphics, sprites, sounds, and what other features I eventually, after getting some hang of writing BASIC, did also realize that what I could create with the machine hardware itself was virtually unlimited. I didn't necessarily know what the commands did with the underlying hardware but I knew if I poked certain numbers into certain addresses I could make my sprites appear on the screen and make them move around.

By the time I got the cassette player fixed by some computer repair shop, learned about tuning the tape head, and I could finally load all the games bundled with the machine, I was seriously hooked with programming and the highly desired games no longer seemed that interesting in comparison. I knew someone sat down and wrote all those games and instead of playing them I could learn to do the same myself.

Been programming ever since.

The only point you can conclude out of these discussions, especially in an interview, that it doesn't matter what the answer happens to be on $CC and $ARCH but you wouldn't want anyone to write stuff like that in the first place.

Failing to recognize the dangers would be an instant fail; knowing that something reeks of undefined behaviour, or even potential UB, is enough: you just write out explicitly what you want and skip the mind games.

We're still in the early ages and must discern hard what AI is good for, what it can maybe do, what it could potentially do and what it just can't do, and move those threshold marks very conservatively. AI is also cheap enough that it's worth shots of experiments. As long as you don't really rely on AI it's easy to test the capabilities of this new conversational autocomplete, and the random gains it offers can be magnificent (except when they aren't, of course).

What has generally worked for me is paraphrasing the old adage "Write the data structures and the code will follow" over to AI. Design your data, consider the design immutable and let the AI try fill in the necessary code (well, with some guidance). If it finds the data structures aren't enough, have it prompt you instead of making changes on its own. AI can do lot of the low-hanging fruit and often the harder ones as well as long as it's bound to something.

Yet, for now, AI at best has been something that relieves me from having to write a long string of boring code: it's not sustainable to keep developing stuff relying on AI alone. It's also great when quality is not an issue; for any serious work AI has not speeded me up noticeably. I still need to think through the hard parts, and whatever I gain in generating code I lose in managing the agents. But I can parallelise code generation, trying new approaches, and exploring out because AI is cheap. AI is also pretty good for going through the codebase and reasoning about dependencies whether in the context of adding a new feature or fixing a bug: I often let AI create a proof-of-concept change that does it, then I extract the important bits out of that and usually trim down the diffs down to at least 1/3 or less.

AI further helps with non-work, i.e. tasks that you have to do in order to fulfill external demands and requirements, and not strictly create anything solid and new. I can imagine AI creating various reports and summaries and documentation, perhaps mostly to be consumed and condensed by another AI at the receiving end. Sadly, all of this is mostly things not worth doing anyway.

Overall, I cringe under all the hype that's been laid on AI: it's a new tool that's still looking for its box or niche carveout, not a revolution.

That was surprising. Goes against the idea that deregulation allows companies to squeeze consumers and earn excess profits.

I've held the belief that an occasional bankruptcy is basically a sign of healthy competition within an industry: those companies going down literally didn't know how to be any more efficient or they could've survived.

Regarding airline business, a crapload of more people are flying now with better prices than before the industry was deregulated. Sure it must hurt someone at one end, eventually. Part of the business is standing through price wars because someone will always lose: the best companies can endure that. While airline industry probably fluctuates as described in the article there are plenty of other cyclic industries. Churn itself isn't anything new.

On the other hand, Spirit as mentioned in the article stopped making profit in 2019. Some years later, chapter 11 filings and then another round.. That's like a 7-year runway (pun intended) to insolvency.

Because fixed costs are what they are, I think, is the reason you can drive the business quite precisely to the brink of inoperation: it could literally come down to pure luck between how full your planes happen to be and how close you are to the next payment of some critical loan whether you can take off into the air for another month or so.

It's very easy to antropomorphise AI as soon as the damn bugger fucks up a simple thing once again.

In principle, this is the kind of right sentiment but for the wrong things.

I can't remember a phone that died because of the battery since the era of Ni-Cd cells in early cell phones. I don't think I've never discarded a phone with a li-ion battery because of the battery. It's always physical breakage or getting too slow to be usable, because of age.

Sure, I don't spend a cycle per day. Not even every other day. That's probably rare, I get that. But much rather than because of dying batteries I'd like EU to mandate

- the phone should come with full keys so that I can own the machine if I want to - or at the very least the hardware must become unlockable once the support period ends - individual components should be made available for independent repairs - repairs must not need software pairing of hardware components on unlocked devices

because of right to own and right to repair which shouldn't be "rights" but nonnegotiable traits of physical properties like they used to be.

Back in the day, I read Applied Cryptography (by Schneier) and clarity rained upon many things.

Dare I say those stuck on nostalgia for pressing keys are demonstrating that they cared more about their own personal experience than about the outcome of their work? Now that coding is automated, we have to elevate our ambitions.

YES. The beauty of programming is and always was that, first, you enjoyed it and, second, for some oddball reason you could actually get paid to do it. And one can't produce anything good unless you actually love working on it which means you want to put yourself working on it. The outcome might accidentally serve the one who pays for it but ultimately what did get the work finished was the sensation when you were reaching the point where you would finally tie things together and see everything you designed come to life and work together.

AI doesn't give you that personal involvement. We can do it but it's a different line of work and we care very little about what goes in and what comes out. We just do the grunt work of connecting the two ends. We're not for a fuck interested in elevating ambitions which is a word that relates to what is outside while all the good stuff comes from the inside.

Google Maps uses Internet access to determine the speed of traffic on your route, allowing it suggest alternate routes if there's a traffic jam.

My phone can pre-download maps into Google Maps for offline use, I've done this in foreign countries where I didn't necessarily have full data connection. There's no reason you couldn't cache the necessary maps on the car's navigation system and let it operate based on that and an incoming GPS signal, never emitting out one bit.

OTOH, if you wanted live data, dynamic routing etc. for your convenience you could explicitly turn data on but then you'd acknowledge it comes with the caveats such as potential snooping of telemetry data.

Admittedly, I would never trust a car manufacturer to actually disable telemetry no matter what they'd promise. So, disconnecting the antennae would be the only reliable method regardless. I wonder if there will ever be a car with a physical radio kill switch like laptops.

Lane keeping is often hard to disable and you have to do it each and every drive, so getting that off permanently and putting the car offline then that is an unexpected bonus. Probably the same also applies for the speed limit beeper that partially relies on GPS maps. Taping over the front camera also works.

There's absolutely no reason an emergency e-call system needs to connect via the car systems such as infotainment. It could be a standalone module that does its own thing regardless of whether the car is permanently disconnected from everywhere. Probably should too, given its nature. And not just could: there are aftermarket e-call systems that do not integrate beyond requiring 12V supply.

This is how cars used to be made. Features were standalone modules: there could be some bus traffic about optional data (wiper module with rain sensor could broadcast that it's raining and body control module could hear that and could be configured to close windows when raining) but they weren't strictly integrated in any meaningful capacity. You could change the radio unit to whatever you liked: if you were lucky you could get one that can actually understand what the other modules in the car were saying and show some non-enterntainment info on its screen as well. Navigation used to be a standalone system that had GPS receiver but nothing else in the car couldn't necessarily tap into the location data.

SUre, it meant some more wires and maybe the features had disconnects because they weren't aware of each other that much but all in all that was a good thing. It kept everything simple, isolated and repairable. Now because of more integration the modules need to know who they're talking to which leads to bizarre things like having to code in new headlights and pair them with other modules or they won't be recognized and just stay off.

What is interesting is that I used to write a program and get a binary executable back from the compiler and I'd have copyright on the source and on the binary. Now I write a prompt and get a binary executable back from Claude and I have copyright on the prompt but depending on my creativity I might be able to have copyright on parts of the output binary. The questions remain: how much, which parts and how the hell could anyone ever tell. This really puts the color of the bits through a vat of dying solution.

On the other hand, separating FE and BE between two teams, necessitating proper interfaces, can often be considered a feature.

Only physical practicalities will prevent this thinking be applied throughoutly: we can't have guardians preventing people from being scammed face to face. But having to identify yourself on a desktop computer and only be allowed to install software vetted by Microsoft and bunch of governments is readily on the books for the kind of thinking that makes these suggestions.

That's where it inevitably leads to. If people can't be allowed to be responsible for X, next they can't be allowed to be responsible for Y, then Z -- all for their own sake. Google taking some mythical "responsibility" on behalf of their users means the users are left powerless and that is that something Google wants more than just being a "good guy" who protects people from conmen.

It's not like people simply couldn't just limit themselves to installing apps from Google Play already, without these "guardrails". Android currently does make it clear that installing unknown apks from an external source is risky and shouldn't be done unless you really, really know what you're doing. No further technical solutions are required for the problem. You can't fix stupidity with technical means.

Counter-examples are France and Japan. Democracies, electoral terms.

A democracy doesn't prevent long-term planning if only the electorate appreciates long-term projects. Democracies can build stuff across parliaments if differences between parties aren't so overwhelming so as to the majority of them can agree on developing something even if the relative power of elected parties varies over terms.

In a lot of countries the major parties agree on many core views and social code because they share a common nation/society, and the political differences happen merely on the edges or linings of the value spectrum. A government of highly polarised parties voted by a highly heterogeneous pool of voters is not ideal for long-term efforts.