PS. I searched and found some in-steerer storage. It's not a headset but essentially a hollow compression plug replacement with a top cap moved to the bottom. I have never seen a road fork with a hole at the bottom so it is likely limited to MTB forks and, since there is no compression in that thing, it might be not very safe with a carbon steerer.

I feel either the gate is making international round trip calls through the internet to some SaaS service. Our it's actually doing a face scan and lookup.

It's quite inconsistent though which is really frustrating. I can look at the imgur homepage feed, but if I go into a specific post and accidentally click anywhere it throws a modal up that can't be dismissed.

If I go on a specific subreddit or post I can freely look, but reddit homepage now pops a modal you can't dismiss.

This is on mobile browsers, of course both sites are pushing their apps.

I am sure it doesn't align with their incentives so they don't care, I will never have an account and never install the app, but why block me from viewing the site if I am still seeing the ads? Does the free ad model just not pay anymore, or is the selling user data model just that much more lucrative that they would rather no user at all if they aren't logged in?

That's not inconsistent, that's a deliberate dark pattern that every social media site uses. Let them see the first page, then when they want to engage: force creating an account.

When you just put a "log in to see this page" up front, people will bounce. When you have them engaged a little bit, chances are they are already invested enough to create an account.

It's not only social media anymore, many mainstream websites have started doing it.

For example on IMDB, you used to be able to read the comments, now they locked them behind a signup box.. it's only a matter of time until they lock the whole site down.

I wish we had the old internet, with simple html forms, texts and pictures.

The peek was really Web 2.0 design, it introduced just enough styles and interactivity to get rid of TABLES but no more than that.

They already AI shadowbanned me and nuke all of my accounts for participating in historical discussions that mentioned violent upheaval of power, thats why I can't login. I appreciate them helping me ween off using the site completely.

Thank you reddit, never thought I'd quit you. And I'm missing nothing but the exact same conversations over and over again.

Traffic from google is probably in the process of collapsing, so these sites are trying to capture all the users they can as registered users before it's gone completely.

And yes, the free ad model is probably in the process of dying, the information that was once given away for free in return for looking at ads is now more valuable sold to llm's who will have the eyeballs going forward.

This will presumably make many on this site happy, since for many years an ad supported open web was consistently railed against.

With the shuttering of nitter if this is what twitter wants then the least they could do is let you create an account. You need apple or google for that. It seems like they shut the front door some time ago and now drew the curtains so people couldn't peer in.

They managed to make it enticing enough for me just to see one person's posts to enter my email but said "fuck off and get the app". I'll have to make do with the 5 posts they show without login

I don't believe it.

I guess that's their traffic so that's their market but ugh. Imagine if flickr or some other photo site was run over by people posting photos of text messags.

I learned that the LinkedIn meta of photos of posts is because their algorithm de-ranks anything with a link, so for farming you should post a picture of text then follow up with a link to a blog post a day later as a comment reply to the post to double-dip the activity.

And, eurgh, so many bad incentives to just make everything worse.

If you earnestly just post a link to a blog, it weights you don't because they don't want people leaving their feed.

And actual text people spend less time hovering than photos of text, so again, down the ranking your post goes.

I don't spend much time on other social media but if Imgur is all just photos of text that won't be an accident, but it'll be what sites optimise for.

Twitter is just the same. It honestly sucks.

Reddit users would post an image in Imgur and the "community" would reply complaining about the lack of context, judging appearances or just being mean in general. The nicest ones would ask users (that would never read anything) to make the images private.

It was a very strange alternate universe.

This is the company that refers to its users as “daily active shitheads.” That’s a real quote.

They’re just screaming and pointing to anything they can so they can lock it down and gain more favorable data to sell and more legitimate accounts to show advertisers. That’s what it always is.

I’m never wrong and I’m tired of fake imposters devs telling me I am wrong at every corner of every single topic when I turn out to be right 100% of the time.

If you truly believe this, then you should probably seek therapy.

https://help.imgur.com/hc/en-us/articles/41592665292443-Imgu...

― Imgur access in the United Kingdom – imgur

I had some success with these for logged-out browsing ever since old.reddit was locked down completely

Reddit isn't so badly impacted, but there are still age-walls around some of the content where it's been deemed "adult" (which encompasses more than just graphic adult imagery).

I dare say something similar also exists for Firefox

[1] https://chromewebstore.google.com/detail/mirrorimage/mglldpk...

So fuck that. Bye Reddit. I'll miss some of the communities.

I remember one soundblaster card I bought came with a Lara Croft demo, that exploited the incredible immersion of real time dynamic reverb.

Genuinely I think game audio took a few steps back from that heady era, the innovation in audio likely didn't sell as many cards as graphics innovations did.

First we had to have the audio processor. Good EAX was available on top of the line cards, and they were not always cheap. Lower end chips got less features.

Then we had to have the speaker setup to have the greatest sound, or needed to get a real 5.1 headphones, which were bulky and never provided the same fidelity.

Then Microsoft changed the Windows driver model, cutting the driver's direct access to the card. All of the timing sensitive effects were gone in an instant. I remember installing the new drivers and getting literally nothing. Sound Blaster was the only card with an hardware mixer, and Microsoft didn't feel like enabling them. Mixing at the DirectX layer killed the cards.

Soundblaster's very closed stance didn't help them either. None of the cards after Audigy2 worked with Linux when I had my desktop system.

After my Audigy2ZS, I moved to Asus Xonar D2X. Its positional audio capabilities were nice, but I mostly bought it for its Linux support and sound quality, and that was top notch in that regards.

Then sound cards became commodity. Everybody stopped making good cards. Musicians moved to audio interfaces, audiophiles moved to DACs.

Just looked to the SoundBlaster website. Internal cards are very limited. One DAC, one DTS enabled 7.1 sound card for PC cinema systems, three game oriented lower end cards, nothing else.

In early 2000s for example, friend with something like a Sound Blaster Live, but couldn't use it anymore as they lost the drivers, their website only had downloads for driver updates, requiring you to still have a driver CD, so no more CD meant no way to get the drivers.

They had not done very much meaningful stuff since the release of EAX and used patents to prevent anyone else from competing with them. Onboard sound cards were by and large indistinguishable from a quality perspective as Creative Labs ones, but cheaper which Creative Labs combated mostly with lawyers as opposed to upping their game.

Some guy after being frustrated with a long-standing bug in drivers for their Creative Labs sound card, dug into the binaries and made a fix for it. During which they also discovered that you could simply flip a switch in the driver to unlock features only meant to be available on more expensive hardware. Creative Labs of course went straight to lawyers to shut them down.

My brother bought the Creative Labs WoW headset which would have its mic get progressively softer until he would leave and re-join the call/voice chat room. They never released a driver update to fix this.

By the time that Microsoft announced no more "hardware acceleration" for sound cards, I had zero sympathy for Creative Labs, I was already convinced that they made pretty shoddy hardware/software and were mostly riding on their reputation from the 90s and some patents they managed to get.

Windows Vista moved away from kernel mode drivers where possible to help address the issue of BSODs which were not uncommon on Windows XP. It turns out that Microsoft was incorrectly getting the blame for BSODs when it was actually the fault of buggy video and sound card drivers.

While Vista was regarded as a "bad" Windows, it laid most of the foundations which allowed Windows 7 to be regarded as "really good" (by Windows standards).

From a hardware perspective, by the time Windows 7 arrived pretty much all drivers had been updated for Vista and had their kinks worked out (mostly, I would still have my NVidia drivers crash on occasion, but because they were user mode now, instead of a BSOD the screen would go black for a few seconds after which my desktop would come back with a Windows pop-up saying something to the effect of "the video drivers crashed and had to be restarted", the real perpetrator now being blamed!). Windows 7 also did optimizations to make things less resource intensive and it also helped that PCs had more RAM compared to when Vista came out.

On the UAC front Windows 7 was also much better, they calibrated the UAC prompts to come up less often, but what also happened is a lot of the 3rd party software which was needlessly requiring admin rights for no good reason (except that it was badly written), had finally been fixed by the time Windows 7 was released.

It wasn't really the cool reverb effects or wave tables, though those were a nice bonus. It was just "I can tell my computer to make sound and it actually makes sound without days of troubleshooting."

Granted, similar things could be said about 3dfx. It's was a 3D card with drivers that actually worked.

And then there's the obvious "sound blasters and voodoos go in my computer, jalapeno goes in someone else's computer" thing.

In fairness on board (depending on the board but on the whole) is pretty good.

Small differences like month and year model can impact oil capacity, oil weight and things like that, the details that matter quite a bit.

I found frontier models couldn't get things like what engine was in a 1994 Nissan Skyline, one of the more infamous and talked about cars on internet forums for decades, with dedicated fan databases that would have been scraped.

Questions like "what air filter do I need for my 1994 Suzuki Swift?" are hit and miss.

Something every LLM user ends up learning is that they're far better used as search and summarization tools than as knowledge databases in themselves.

Edit: this applies to service manuals too

Mine, too.

Did you fact-check the output?

I've found the bot to be particularly bad at stuff like producing accurate lists of parts to replace during automotive projects.

That car is a ridiculously-common Honda Odyssey with an engine that is even more-common.

I do sincerely wish you good luck with your suspension project.

So local and cloud agents figuring out the best solution together with none of your time needed.

It keeps itself grounded on sensor input. One principle per wheel. assert only what you can sense, claim only what is verified, label anything interim loudly, and report failure plainly with no silver lining. Everything above those four patches is just suspension.

I'm having a hard time understanding how you find any sort of accuracy in Q3, when I use it with BF16 and it's hardly usable due to drastic hallucinations and inability for system prompt following. But, if it works for you, that's pretty good! Guess I'm jealous :)

Anyone not in the US feels this even more since so much online is US hosted, 300ms for every little interaction adds up quick.

If your software has the affordance of a waiting dialogue or loading wheel for many of its UI controls, you are building with this default blocked assumption. Even if you are building something web based, ask yourself if that's actually necessary for your software or if you could build it differently to avoid constant UI blocking.

On top of that: Creating software that isn't outright wasteful in terms of performance isn't even hard, it's just a matter of not doing ridiculously dumb things. The problem I've observed in teams I've worked with is that the majority of programmers don't even know what the dumb things are, and wouldn't know how to even approach making something that's halfway fast.

Edit:

Unfortunately I think posts like these are only going to make the problem worse, because now people are going to ask for voodoo solutions to performance issues, when the answer to their problems was usually just "Maybe stop creating wasteful intermediate structures and just walk an array like a sane person" in 99% of cases. The first leg of any optimization journey in the average programmer's code will likely net tens or hundreds of times faster code, and that's actually all people were asking for.

The knowledge required to make those changes and understand them is fairly minimal, but the kinds of people who have to create spinners for webmail interfaces, have their application add 150ms on top of whatever round-trip you have for processing things counted in 5 digits, etc., have never bothered to even learn those things.

Non-tautological rephrasing: When optimizing code, first actually just de-slowify it, and that should most often be plenty enough.

What you point out is slowness once you hit the entry point. Go, or similar languages, as a server language platform could have solved that problem from a computational perspective. But it did not for the most part. In my opinion people choose the faster stuff because it's cool and they have more wiggle room to cram in to get back to the slow status quo.

Everything is overengineered, software or distributed architectures, sound to naive human logic but alien to computers. It's an cultural problem, development is so deeply entrenched into "business logic" that the minimal viable and computational economic solution isn't even on the table. I don't even think it has to do with cost or feasibility, it's just that your random e-com manager wouldn't know what to do with you, if a programmer really starts talking about hardcode tech stuff.

Another friend, worked at a company, that got a new manager (I think as a result of a merger), and that manager halted all work on "yak shaving" projects. These "yak shaving" projects were things like logging, and debugging, and some kind of integrity-verification. When asked why they were being halted, the new manager said: "none of our customers asked for any of these things". When told that these things enable the team to produce a better product for the customers, the manager (I am told) looked at them with confusion and suspicion. Those projects were never improved since, and the product stopped improving as well. I am not sure if it affected their business (the pandemic was much more distortive).

What you call "business logic", is not even logic, and it has little to do with business. It is what Feynman called a "cargo cult". The obvious name for it is "cargo cult business management/logic".

It truly is embarrassing and shameful that after decades of idiotic decisions, it took a _trillion_[1] dollars of investment into a chat-bot technology, to finally crack open _one_[2] door to slightly less idiotic decisions, while opening dozens of new doors to decisions of an unknowable character.

Most companies (and, consequently, their engineering organizations) are simply _cosplaying_ as the things they are supposed to be.

I do not see how an AI assistant (or any kind of assistant or consultant) can save these fools from themselves. The only logical explanation is that most software companies are cursed -- you would have much better luck engaging a witch-doctor.

[0]: Nobody else knew C or C++ either. The fact is, that nobody cared. In fact, even Go would have been a better choice than raw Python, but nobody cared. Even Common Lisp (which is at least as abstract as Python, and has native execution speeds (GC and runtime type-checking can be turned off for compute-heavy workloads that mutate data in-place)), is a better choice, and yet, an _abundance_ of obviously superior options (all implemented and maintained by obviously superior engineers) was not enough to prevent the organization from choosing an inferior one, and using it stupidly (without a fast native-code component).

[1]: I see estimates from hundreds of billions to a trillion, depending on how you count it.

[2]: The performance door, if Luu is correct.

God forbid you say anything about it in a code review lest you get shouted down about premature optimization.

"This other unrelated thing in the code is slower, so writing this correctly is a poor use of time!"

I have been using the proprietary NVIDIA drivers for more than 2 decades on various hardware, both desktops and laptops, mostly with Gentoo Linux.

Opening an OpenGL context or any other OpenGL operations have always been instant.

Try turning off wifi and see if it improves.

Things like this really pushed me to everything local systems. I’ll move actual files around if I want to do anything on the network. Or sometimes even use cables! Shock, horror!

The original design had the speakers setting up a private mesh network, and the app would send commands directly to the speakers via your LAN. Then, they got the brilliant idea to route commands via their cloud service. The app would send commands to an endpoint, which would send them back to your speakers. Imagine trying to smoothly fade volume with a WAN hop. This went over as well as you’d expect, and they’ve since promised to work on performance. Thus far they seem to have been doing so; it isn’t as snappy as the original, but it’s quite a bit better.

Device developers, stop doing this! You people realize that LANs exist, don't you?

I argued breathlessly against it for days. I’ll never forget the sales chad raising his voice to shut me down with a cop-out:“This is the way the industry is going!”.

It’s not the developers making these changes.

Not saying that’s what you could or would have done, I’ve just gotten to the point in life where I’m alreaover it, ready to throw it back at them. Maybe it’s from living in this part of the world, but our plumber said “always be ready for people to be mean to you“ and while it doesn’t make for a very peaceful life, it certainly makes for fun ripping heads off.

- Access points that don’t let WiFi devices talk to wired devices.

- Office networks that don’t repeat broadcast discovery traffic into different segments.

- People in McMansions who don’t understand extenders and use two different SSIDs for each half of their house or for indoor vs poolside.

- Phone is on cellular network, speaker is on WiFi, “controls don’t work”

- Network teams who won’t “open the ports” or configure mDNS or Zeroconf or Bonjour but will let port 443 to the internet.

- people who want to turn their speakers on at home while they are at work, for their dog.

- people who want to turn their speakers off at their second home after they returned from holiday and left the pool party music playing.

- diagnostic logs that would be nice if they went somewhere.

- People who lost their phone and want a website on their laptop to control their speakers.

- people who have their speakers nicked and want to login to your website to see their speakers checking in and “remote wipe” block them.

- People who want the status of all their speakers live in their phone app, even the ones at other properties.

- tons of buggy low quality, low cost, network devices (switches, hubs, cables, routers, firewalls, NATs).

Just about the only thing which is used enough to be reasonably trustable on any random customer network is HTTPS to the big CDNs and Cloud providers.

[1] https://news.ycombinator.com/item?id=49376040

Again this is mostly our biases playing us. Within HN and similar communities there are a lot of above average and caring developers. Those who don’t care aren’t going to be here to look like they do.

Unpopular Opinion, but if you have absolutely zero say in the content of what you're developing, and just take orders from JIRA, you shouldn't call yourself an engineer. You should also keep your eyes open for a better job.

You are starting to get software with ticket driven development layered around glue code for existing libraries. I see no problem with libraries, it is just the architecture and vertical understanding that leaves a lot of performance on the table, because refactoring insanity takes resources and a lot of talking, understanding and convincing to be done.

Doing this across big teams starts to have downsides. So one team doesn't have a particular use case implemented or understood it and does not want to support it and you run code to compensate for this.

Best example in a monolith case is oracle...

    "Do not fall into the trap of anthropomorphizing Larry Ellison. You need to think of Larry Ellison the way you think of a lawnmower. You don’t anthropomorphize your lawnmower, the lawnmower just mows the lawn - you stick your hand in there and it’ll chop it off, the end. You don’t think "oh, the lawnmower hates me" – lawnmower doesn’t give a shit about you, lawnmower can’t hate you. Don’t anthropomorphize the lawnmower. Don’t fall into that trap about Oracle."

I feel this is so much real. Like if there were two kinds of companies: the ones who deliver, they care about their product but most of all they care about their customers, the managers get their hands dirty and everyone pushes towards the same direction; then there are companies in which you open a ticket and wait for two weeks for something that should take 5 minutes, customers and product don’t matter because you’re focused in cost attribution and no body does anything if it doesn’t come in your JIRA board, the managers are all coming from consultancy companies and all they do is finding someone to blame.

“…the structure of a designed system mirrors the communication structure of the organization that built it”

https://en.wikipedia.org/wiki/Conway%27s_law

But if I were to pick one single thing that would speed up the most UIs across the board, it would be poor handling of the UI in networked systems. As you noted, that doesn't mean eliminating them, it means handling the inevitable in a way that doesn't tank the UI feel.

Somehow I don't think I'm the only one who presses a button and when nothing happens presses it repeatedly until something happens, or I kill the app, or even power off whatever piece of shit computer I'm using.

The problem usually comes from inappropriately arranging the systems of record such that information needs to be communicated beyond the scope of one computer in order to satisfy a single logical request.

Moving information between physical processors tends to be significantly more expensive than local computation over that same information. JSON serialization is a really good example of this. You need a network with bandwidth in excess of 10 GbE to begin overtaking simdjson.

SSR or SPA doesn't really matter if the server still takes a minimum of 300ms to compose any kind of response due to how its database or other infrastructure is set up. Information theory doesn't care how clever your loading indicator is. If the information isn't available, we can't do anything meaningful. Stringing the user along with psychological tricks is a lot cheaper than hiring a skilled developer to do it the right way.

> Information theory doesn't care how clever your loading indicator is. If the information isn't available, we can't do anything meaningful.

Yes we can - we can fix why the information isn't available. If someone said to you "sorry, we don't have the info because the other thread is doing Sleep(5000);" you'd call them an idiot right? You'd go and delete the sleep call to make it faster. Most real problems are harder than that, but there's no fundamental rule saying your database has to be slow. Ping time across your LAN is probably under a millisecond, so where are the other 299 milliseconds going? Is your database doing a full table scan? Is it using spinning rust for frequently accessed data?

As to your database comment, IME most of the time the bottleneck is the ORM and/or language. The amount of work an ORM does to generate a representation of a row is frankly shocking. Not understanding the cost of context-switching is the language half of it: Python, of course, is single-threaded, but you can use greenlets to cheat, because they’re I/O bound — except for all of them serializing behind a single process handling serdes for the queries.

* Must feel very responsive * Network requests can take up to 500ms end to end

Or just pirate the software and let them sue you for pirating, which you will win since you have a license, even though the computer thinks you don't.

I would guess Canva already does something like this.

This gave me a chuckle because I personally hate things like watching the browser jump through 50+ redirects when logging into a website.

We've come full circle.

With a fast backend ~1-5ms response times (not even that fast). Streaming compression over something like SSE to keep your response sub 1kb packet (roughly an ethernet MTU).

With a push based model, pushing data to a user is half their RTT latency. They will only experience their full RTT on actions they trigger.

Now the network to you is distance to the server (not your rail/nextjs backend taking 400ms). Things like 4G and 3G are fine. The real problem is when you have such bad signal you effectively have no down or up.

When it comes to improving performance by a few ms, or implementing a new feature, business people will always choose a new feature, unless the current performance is unbearably slow (we're talking regular 1.5s+ wait times for BE response).

And it's not even a modern problem, legacy software written 20 years ago has the same latency than most modern backends from my experience.

Even though benchmarks suggest this sort of performance should be trivial, most real-world servers I have interacted with do not reliably managed to process a request, make a roundtrip to the DB, and return a response in <5ms

Hell, for a lot of projects you don't even need to get that fancy. Run a single server with an embedde database, running Go or Java and you're good to go.

It's one thing not to e.g. spend the extra time to ensure everything is cached and mutations are queued up. It's another thing not to do the bare minimum to ensure what is already available and working locally is gated on the network being up.

Case in point: The other day I was checking our train tickets in an app, and the network was awful, and the train tickets which the app has local copies of took 30+ seconds to appear when the network went down. Everything I needed worked once the timeouts had been hit, it was just ridiculously slow waiting for timeouts for functionality I wasn't trying to use to be hit first.

I wish Atlassian listened to you.

I'm making a simple plugin for Gimp that sends the active layer to a model with a prompt; on Macs by default the UI waits for the request to come back or timeout; on PCs it doesn't, so the modified layer appears unexpectedly. The Mac experience is better IMHO and I will replicate it in the PC version rather than the other way around.

https://nextjs.org/docs/app/guides/prefetching#hover-trigger...

In my view, websites should not take seconds to load with gigabit fiber. Whatever happened to "mobile first"?

Funny thing is it apparently predates JSON. It's a bunch of data[foo][bar] = baz; - go look.

(Website's in German obviously, and a surprising number of German electronic terms are very different from English. They use two different words for stranded and non-stranded wire.)

I don't think the current crop of fullstack engineers would be hard pressed to know what a "markov chain" is, but in theory yes, you could emit a bunch of speculation rules[1] based on your predictions.

I should also say that markov chain based approaches have been used for fraud detection, e.g. identifying checkout anomalies by detecting the sequence of web pages that they clicked on, amongst other factors.

[1] https://developer.mozilla.org/en-US/docs/Web/API/Speculation...

This might seem wasteful, but if the web were content addressed instead of server addressed you could then be serving that cache to your municipality even after it became disconnected from the rest of the internet. Which sort of recasts it not like wastefulness but instead like fault tolerance and preparedness.

We could maybe even dispense with the servers entirely.

There are so many different ways to build a web. Why does it feel like we've landed on the worst possible one?

This is already possible without content addressing with CDNs. They can serve content from a local cache even when the host is disconnected from the internet.

Welcome to Next.js

The .js part makes me think not.

  <script type="speculationrules">
  {
    "prefetch": [
      {
        "source": "list",
        "urls": ["/checkout.html", "/thank-you.html"]
      }
    ] 
  }
  </script>

I should be able to get the lay of the land without trusting the site enough to blindly execute whatever code it points me at. It's needless attack surface.

Also it's not really pointing me at data, its pointing me a certain kinds of requests which I have to trust will be responded to consistently. I'd much rather have a hash so if I have that data lying around I can just forgo the request entirely and use what's present locally.

1. You need write access to the server if you want to add one

2. The server could change its behavior at any time and there's no way to know that caches now need to be invalidated

3. If something goes wrong with connectivity or name resolution, there's no fallback since the authoritative thing was not something durable like a trusted human via a public key but rather an ephemeral thing: a named server which has pinkey promised to stay online.

It asks the user to treat a server like a trustworthy source of perisisant data.

But there's no reason to couple these kinds of trust. The skills necessary to persist and traffick data are orthogonal to being trustworthy about content. Coupling them creates needless load on single sources of failure which are simultaneously single points for corruption to target.

Trust people, not servers. Use digital signatures to validate that what you're seeing came from those people.

<a> tags are the opposite of this. They encourage us to trust servers by name, which isn't really working out.

Don’t know about that, pretty much everything is hosted on Cloudflare, Azure or S3 these days and all of them have at least one CDN on each continent.

After traveling around in places with very poor wifi/phone data speeds. I couldn't agree more with you.

It's infuriating when it's obvious that the developer of an app only ever tested it in a simulator on their dev machine on their super fast WiFi. It never seems to connect with those people developing a mobile app (or web app) that the "mobile" part has a meaning more than just on a handheld device.

We don't turn faster hardware into faster programs, we turn it into more program. AI isn't going to change that. We'll just get even more program because the optimisation has freed up space for that.

Unfortunately most of the time, the more program isn't for our benefit. I note that by far the heaviest program I use is my web browser. The one thing I don't get to choose what code gets thrust upon me.

If I want to watch streaming videos, I don't have a choice about how I do that.

Fine Firefox is basically a bloated YouTube app. That doesn't change the fact that it is inefficient (from the pov of my CPU) for doing that.

Obviously agent access goes away with internet failure but the state doesn’t need to… we use CRDTs and a virtual FS. There’s a toy-ish version of the harness at https://ourhearth.ai … if local first is interesting to you I’d love your feedback

The optimisations the article is talking about would help even with this problem if backends responded faster - although not as much as actually avoiding unnecessary network requests in the first place, of course.

If there's a connection to your services outside of the user's machine you can control all of that.

second is on a smaller timescale. so many features and crap that is never asked for and never used is crammed into software so the systems that execute it are just juggling pretty much dead code in and stale data in their caches all days long.

We as an industry should use AI to enable a standard of software quality that was previously uneconomical.

The issue I think you’ll run into is that they’re lacking users and kind of just worse versions. Usually because people who say things like this, don’t actually want to be personally inconvenienced to switch.

  PING news.ycombinator.com (209.216.230.207): 56 data bytes
  ...
  --- news.ycombinator.com ping statistics ---
  40 packets transmitted, 40 packets received, 0% packet loss
  round-trip min/avg/max = 154.980/155.832/156.990 ms

  round-trip min/avg/max = 164.218/164.860/165.764 ms

  rtt min/avg/max/mdev = 201.881/245.543/350.600/48.713 ms

We would give them a plausible sounding fake key then they would give us a new real key. Nothing seemed to get verified or cross checked but it worked at least 4 or 5 times for our little gang of proto-nerds.

But for those in the US, wouldn't it all be a bit familiar? Whenever I watch a movie set in my home country with home accents and locations, it always feels a bit too familiar and it can cheapen the feel a bit.

I was watching Monk recently, and it feels kinda neat seeing a show shot in San Francisco because I used to live there. I wouldn't say it feels "cheap" though.

If they are adding so little value as to be as transparent as a pen and paper then why use one at all? Transcription doesn't need an LLM so that's not what you're taking about I assume.