iOS has Narwhal 2, as well. It’s got its own subscription to defray the API costs but it’s a reasonable price.
2,175 karma · joined August 2, 2012
I’m not even talking EVs here. Why is a Hummer legal to drive when it causes disproportionate wear on the streets, can’t fit adequately in a lot of parking, and will essentially obliterate any other vehicle it hits? It doesn’t even have a reasonable commercial purpose beyond wrapping it with advertising and using it as a parked billboard as far as I’ve seen.
And as far as EVs go, my Ioniq 5 is a little over two tons and has the wheelbase of a Palisade already. Do you really need a whole other ton and a half to add a third row? On my car I’m pretty sure you just have to square off the roof and allow some overhang in the back. It’ll need more battery, but a ton more? Empty pickup truck beds aren’t all that heavy either, for that matter.
I can’t imagine this type of mass inflation has been as rampant in Europe and other areas that value small cars. We Americans have always been in love with displacement, whether it’s coming from the engine or the chassis.
In particular, JPEG has intelligence encoded about how graphics are displayed, what detail we won’t notice is missing, and what artifacts we won’t notice are present, much like the psychoacoustic models behind lossy music compression schemes like MP3.
But we had to feed an encoder that by way of algorithmic design. It’s hardcoded intelligence, like any other function, but with a lot more outside knowledge required to do it right than a sort or swap.
I’d call an LLM a more general problem solver. It can write cogent limericks, convincingly screw up math, summarize papers it’s never seen before, generate book plots or character arcs based on specific requests, translate to a language you just made up and explained in the prompt, etc.
The intelligent bits are emergent and can do something reasonable with novel input, even if it doesn’t closely resemble the exact material it was trained on.
The comparison would be a process that could lossy-compress any kind of sensory media possible with no perceptible loss, based solely on its training on human capabilities and how the reproduction devices work—i.e. it could create the JPEG algorithm, not just perform it.
If I weren’t already a Pokémon fan I wouldn’t have bothered with Palworld, because I don’t care much for Ark (the game whose loop it largely duplicates).
And the fact that Game Freak can’t seem to code a mainline Pokémon game that runs well on Switch certainly did help whet my appetite. If I’d been more satisfied with Sword/Shield or Scarlet/Violet, I probably wouldn’t have jumped on this one. Unfortunately, neither runs very well—particularly Scarlet/Violet, which was dumped rough and flat out abandoned for performance patches.
As the other commenter said, Palworld is not all that dissimilar to the open-world title Arceus, which is coded competently enough. But I like having more to do in my open world than just fulfilling challenge lists. If there’s story in Arceus, I peeled off out of boredom well before it presented itself. At least in Palworld I can build a base, etc.
So yes, my interest absolutely had something to do with the decline in Pokémon games for this latest generation.
It may surprise you to know that a) gamers cross genres on a regular basis and b) the Pokémon franchise itself is multi-genre (the card game, Snap, and Go! being big obvious examples). Genres basically just don’t matter to this equation. We’re here for the monsters.
"copilot": {
"disabled_globs": [
".env"
]
}
I don't see a way to disable all the collaboration features, but it does look pretty difficult to do it by mistake. You have to add collaborators explicitly.
The other poster had a good point. A marine-class alloy would make a big difference in coastal and salted road areas.
“…they didn’t clearcoat it?!”
Tesla is great at batteries and wheeled computers, but man, they have some serious blind spots when it comes to building vehicles.
I wonder if you can get an aftermarket ceramic coat or similar protectant on it.
The degree of drama I’ve anecdotally seen them stir up seemed to support my hypothesis. I avoid them now.
I will admit I assumed at least one of my direct responses was from someone involved directly with the development or design, or I probably wouldn’t have taken the confrontational stance I did. A year or so later, it does feel a bit accusatory, as you say.
All said though, I also don’t use that forum anymore (though I sometimes land on it from Google searching for plugins or tips) and I certainly don’t submit bug reports.
Obsidian’s biggest flaw remains, IMO, that there’s not a good way to report an issue with any confidence it’ll get an even chance of being addressed.
As far as I could tell, at least at the time, if the devs didn’t jump on it immediately, it’d end up automoved to a graveyard before it could ever possibly get traction. When things felt like they started getting actively argued down without considering user stances, that’s what tipped me over.
But, as I said in another comment, I eventually came back to Obsidian and renewed the commercial license so I could use it at work. It is a good system. I just think it’d be that much better with a more effective feedback loop.
I kept trialing alternatives like VimWiki, Joplin and Logseq, but everything else is even quirkier. Org-mode is about the only thing that seemed really competitive, but since I’m not an emacs person there’s a big ramp there for me. Plus, as with most of the alternatives, that loses Markdown compatibility entirely.
Re learn new hotkeys, that’s actually not been a huge issue. Most of them simply aren’t mapped by default, which is its own pain. I did a lot of bouncing between VSCode hotkey lists and the Obsidian hotkeys UI to align shortcuts. At least they do enable you to remap most every UI action. I haven’t used the built-in vim bindings, but supposedly they also work fairly well, fwiw.
For now, Obsidian + Obsidian Tasks just does way too good a job for my work journaling for me to completely ignore. Plugins do work around most of the more questionable behavior, though it does sometimes make for an inconsistent experience.
I have an Alexa list called “Grocery” that does a 2-way sync, and use it to accelerate my online Safeway orders via AnyList.
You can sync to the default Amazon Shopping list too, but I find it works better if you have a secondary one specifically for sync.
That was the deal breaker for me on Apple keyboards. I could deal with the F-keys being a touchscreen but I use Esc way too much for muscle memory to not work. In practice I remapped Caps Lock to Esc, but it was still a pain not having it in the right place.
I know I wasn’t the only one with this opinion. I thought touchbar Esc was a long acknowledged usability don’t at this point. Even Apple changed that one up pretty quickly.
This is from my Steam review (one of two ever, I liked it so much):
> Man, what a trip. I’ve played the NAND game and MRHD, among others, but never quite got to the “build a computer” endgame. I did with this one. At this point I’ve built a 256-byte RAM system that does six math instructions, six conditional jumps, and subroutine calls using its own stack—then developed my own assembly language for it which I'm now using in the endgame to solve more traditional programming puzzles.
> And I designed and built the entire architecture for it myself. The initial levels are mostly "one solution only" problems that each results in you designing a component. But by the time you're at midgame, all the decisions are yours as long as the output is correct. Previous problems tend to hint towards partial solutions of later problems, but very little is given to you outright. That gives you an incredible sense of accomplishment for what you put together.
That said, unless they improved the bit where wiring tends to merge together and virtually short out during edits, it can be a little frustrating once things get very complex. It's not enough for me to not recommend it, but there was a point where I felt like I was having to master the tricky interface quirks as much or more than the logic. Shenzen IO did that part much better.
I’m surprised it didn’t make more of a splash.
The current 400V architecture would charge even slower than the raw math would imply, because it requires the car to handle the voltage difference internally. Going through that path bottlenecks the charge rate at something Chevy-Boltish like 50kW that's simply not very viable for road trips.
It might be a "legacy dealers can't sell even good EVs because they don't know enough about them" issue though. Really hard to say, but that definitely would match my personal experience talking to a number of them.
A few years later, my Pascal background sailed me into a half-decade stint as a custom app dev working with Delphi. That, in turn, led to a job at Borland testing the Kylix and C++Builder IDEs. Good times.
I still miss Delphi. Nowadays it's normal to have IDE plugins to the point it's a dealbreaker if they don't exist. But at the time the idea of a component library and coding environment that was easily extensible in its own language was pure magic. I had so much fun playing with both VCL and the IDE itself.
It's a shame Borland left the grassroots devs behind in their quest for the enterprise market, and more or less killed any growth in community adoption. It was a really cool setup, at least through Delphi 7 or so.