Lots of interesting takes that I think I disagree with here, although I mostly write Markdown rather than read it:
> they’re hamstrung by the terminal itself, which is almost always monospaced and thus fatiguing to read.
I recently re-built Blue, a minimalist text editor inspired by the Turbo Pascal and Turbo Basic editors of the late 1990's. It uses a fixed width font, because I prefer it.
I never use the physical touch on the MacBook Pro or MacBook Air. It’s one of the first things I configure so that a light tap is a click. It somehow feels “faster” to me.
Three finger drag. That was the best and unique thing about apple touchpads since, like, early 2000s, but then it was buried deep down the menus and forgotten for some reason. But seriously - try it, you might never go back.
Ender 3 V2 that I paid <$250 for about 5 years ago. It paid for itself on the first print job where I repaired some Samsung stove knobs where replacements were $400 a set.
I'm now considering an upgrade and I'll likely just go with the Ender 3 V3 Plus (bigger bed, auto leveling, still an offline printer) and < $450 for cost.
It's been a fantastic printer for me.
I use Cura, stick with standard settings, use Sun PLA+ for all my prints, and the only thing I really need to do is level the bed sometimes.
I went to work at a BBB office once. They turned all their computers off at night and every morning they were back on. It was just "normal" for them.
I can't even remember what problem I was troubleshooting. At the time I was working on IVR systems.
Anwayz, I was working late in their office. Everyone had turned off their computers and went home. At exactly Midnight, every computer in the office turned back on.
I walked around the office looking at desks wondering what had happened. On one persons desk was an alarm clock with a very quiet alarm buzzing. I checked the clock and it was set for midnight (probably a default). About two minutes later it turned off automatically.
I turned off computers and re-set the alarm to go off a few minutes later.
When that alarm clock went off it somehow caused either draw or feedback in the wiring that caused all the computers to turn back on. At the time I wondered if it had something to do with wake on lan.
In any case, I suggested that person take their alarm clock home.
Apparently, data centers typically use evaporative cooling (I guess like a Swamp Cooler but on a whole different scale). This is cheaper than using compressed systems like we use on our homes. The water evaporates.
At a global level the water stays around but at a local level it "vanishes into thin air".
Same. I hit limits after 45 minutes. I'm on a measly Pro plan. I'm usually building small, open source projects, often from scratch. I only work on these projects in a 2-hour window in the morning. This is my "free time" development. I hope this change helps, because I was days away from switching back to Codex, though I like Claude Code a bit better these days.
I also hope that the fact I had OpenClaw in my sandbox once is not why I hit these limits so damn fast. I don't use it anymore and I've tried to rid my sandbox of anything "openclaw" but it is in my git history in various places on various projects. Claude doesn't seem to be transparent about this limitation.
I kinda assume the dealer does this as part of any service they do. Either that, or they update some other way. My software notices went away when I had my service done, even though I’ve opted out of everything (and verified again after).
Even more tangential: Kia declined to cover an engine failure, under warranty that was extended by recall because I change my own oil.
Kia's engines are known to fail predictably even within first 100K miles. They extended their warranty because of it. But then they weasel out of it unless you hire an attorney and go to war.
This doesn't require research. Just reject by default and concede if a lawyer shows up. It doesn't cost any money to have a default denial policy and saves millions.
Yeah, because you allegedly consented to them being able to update your ECUs via the mobile link in the cars when you bought the car.
As if I needed another reason to keep my 2014 skoda.
If i ever have to get a new car, i will disable telemetry, and i will buy it either without telemetry, or with the agreement that i do not consent to telemetry.
(read the fine print before getting a new car. the shit they can do that can go wrong and you have to pay for.. no wonder old cars cost as much as new ones.)
I assure you that “old cars costing as much as new ones” isn’t the result of the market force of people reading contractual fine print and/or freaking out about telemetry. Concentric circles of echo chambers over here.
The main reason is more tangible to people. It is more reliability and simplicity. For instance the Toyota Tundra used to have a V8 that was pretty bomb proof. But over the years, manufacturers put in more efficient but more prone to problems turbocharged smaller engines. The bearing clearances went down, thinner oil then can be used which is also more efficient. But the margin for error when you are putting what used to be a performance engine in a car is much smaller and there have been issues. As car prices have gone up, people value a time tested drivetrain. There have been a lot of problematic CVT transmissions too.
The Chinese government banned Tesla vehicles from entering (Chinese) military bases. This is due to the prolific number of cameras streaming live video to a hostile (to China) organization/government. One can find blogposts by analysts who show that the upload stream from Tesla vehicles includes cabin audio.
I’m not worried even a lick about what cars cost electronics or otherwise. My primary factor in selecting a vehicle is my physical safety; after that it’s electronic surveillance.
> I have never met anyone in real life that's concerned about telemetry on their car
You mean you've never had a conversation about it. You can't know if you've met somebody that has that concern unless you've broached the subject explicitly.
1. get a _real_, unabridged service manual. that takes some darkweb experience nowadays.
2. identify anything that looks like capable of housing a cell modem. that takes some understanding of contemporary car electronics
3. deny RF interface to units identified. that takes some understanding what RF = radio frequency interface is and also getting rid of fear of disassembling significant portions of your car.
That is the least of your troubles. SOS is the telemetry you wanted to get rid of in the first place.
And chances are you would have to get rid of 2/3 or more of oem electronics.
It'll end up a prototype vehicle or something, with custom ECU and stuff. On the bright side it will belong to you and not to the some mckinsey guys running those insurances and whatnot. It has been done too, although I personally prefer to just use vehicles that do not require this level of effort.
The other day there was a thread on unclouded tractors what I missed and I must tell I love my Universal 445 made in Romania in 1989. For all its quirks, it just gets the job done, no connectivity, no nothing, it's an unbreakable 3-cylinder diesel that just works.
It works depending on the manufacturer. Honda places the TPU in the dash behind the head unit. Use some spudgers and you can disconnect and remove the TPU. Takes 15 minutes at most.
I would argue that senior engineers, of which I am one, are more of the problem than junior. We build fancy custom components when we should be using the existing ones.
Yes, the (senior) product and design people are part of the problem too.
What? In my experience the true seniors are the ones pushing hard for simplicity while the mediors build overly complex messes that one needs to be a rocket scientist to understand.
> they’re hamstrung by the terminal itself, which is almost always monospaced and thus fatiguing to read.
I recently re-built Blue, a minimalist text editor inspired by the Turbo Pascal and Turbo Basic editors of the late 1990's. It uses a fixed width font, because I prefer it.
https://github.com/codazoda/blue
reply