wryanzimmerman

As someone who travels a lot, SMS based app stuff is one of the most annoying common problems.

It’s easy to find a way to get internet anywhere, but getting an sms message at a phone number is way harder (or easy but expensive); bonus points if you restrict it to local phone numbers only. Lots of countries require ID checks to get a local number and the system breaks with foreign IDs.

JavaScript driven SPA is fine as long as everyone remembers that the entire and only point at the end of the day is to create HTML.

That’s why you send them the link to the prototype, which opens in their browser, not the figma link.

That’s like half the point of prototyping software vs graphic design / illustration software!

Non-designers want to see “the site” open in their browser and be able to click through the pages, instead of use some design app—that’s like half the point of figma.

Garmin watches can be used this way, but it’s not quite as easy; you can even mount the watch as a USB drive and access a lot of the data that way if you want.

I did hit one issue once with maps on my fénix 7 where I had to plug it in to a windows computer specifically.

I disagree slightly; I think there’s an important thing here which was a little bit glossed over in the article.

The original code established a pattern and left space for where and how to add code to handle edge cases, when they arose, whereas the clean code solution was implemented as though it was the complete and final solution.

A first draft is often incomplete, and in an oversimplified first draft, it’s easy to pull out patterns and remove “duplication” which is a result of the simplification, not an inherent feature of the problem being solved.

And the parent comment said “47% wasted power … extra second … would offset half of that” and 47% of four seconds is about two, half of that is one second, so I’d say that was shockingly accurate, wow!

But based on this it seems like the right comparison is between a three year old iPhone and a brand new mid-level android because they’ll last you the same amount of time, and three year old iPhones aren’t very expensive (though it depends on where in the world you live. In plenty of countries ~2yo iPhones cost the same as brand new iPhones at US prices, because you can use them for so much longer than local market android phones).

Sorry, wrong comment

That seems kind of odd, my iPhone 12 Pro has zero issues with things like that and it’s three years old.

I did upgrade a few weeks ago because the iPhone 15 cameras are amazing and I care a lot about that but I honestly had zero performance reasons to upgrade. I’ve never had an issue with a 5-6 year old phone and I always keep my old phone as a backup specifically for banking.

You can’t “fix” a leak, you have to revoke the involved secrets. Editing / deleting the answer is irrelevant.

They didn’t, they were passing by, and eventually headed to an area with coverage.

There are several states where you can form an LLC without making your information public. In New Mexico you don’t even need to tell the state.

I can’t tell if you’re talking about the US though, if you’re referring to other countries it may be much more restrictive, lots of places seem to require ID and registration for basically anything.

Macs manage memory and swap in a way that makes them feel much more responsive when you have a lot of common applications open at once (or something like a lot of browser tabs at once), but if you’re literally doing a single task that uses a given amount of ram, you need that much ram or you’ll slow way down.

I think a large part of the black background choice was to hide the missing bodies; any light past chest level is going to push this into uncanny valley pretty fast because the modeling ends at the chest like talking Greek busts.

Totally agree that it’s a stylistic and presentational decision and not a computational limitation.

What do you mean by there by default?

There are a lot of ways you could send a valid response without including that header or tag, any policies are not one-size-fits all and could be different. Maybe you’re using a full-stack framework which is managing it for you?

Or maybe you’re confusing it with CORS?

I think that’s more or less what this project is working towards:

https://hyper.is

All those points equally apply to web apps and that’s exactly why web apps are becoming the default starting point for any new product.

How would you make the GUI work well over SSH, unless you mean having the GUI installed on the client device and only connecting to the host over SSH?

A huge part of why I keep my workflow 100% terminal / TUI is because I know I can use anything with a solid shell (even my iPad or my phone) and instantly have my full workflow exactly where I left off with every single program looking and working exactly the same in exactly the same state.

What the parent comment is saying is that you can connect via usb and access the data that way.

Of course, the easiest way to see the raw data is to write a python script to plot it, so it’s not exactly the most user friendly, but it’s technically possible.

Even better than that, while some of them can sync over wifi directly, most of them sync over Bluetooth, to your app which must be logged in, which does nothing except use the phone’s internet connection to upload the data to garmin, and then the app needs to re-download all the data from garmin’s server before it can be displayed in the app.

So they can sync over Bluetooth… but in a format that garmin’s app can’t use or understand so you must be connected to the internet to actually see the data.

For a device which generally should work with bad/no internet, it’s completely insane.

I built a CMS backed by it to build sites that are mostly data, but have a few text blocks and images, so since all the data entry was in Airtable anyway, moving the rest of the content there made sense and now lots of small dev tasks can be done with zero dev time (change gets made in Airtable, product manager triggers the CI build, CI build pulls everything from Airtable)

And it was worth it to give up the $4-5k / month instead of going to an employer without a COI policy and keeping the dual income streams?

The vim equivalent of that is visual mode, eg `vwd` which is exactly the same structure as you’re saying you want from kakoune.

So vim is verb-noun for simple things, but if you want, you can use visual mode if you’re doing something more complex or just want visual confirmation first.

Sublime with first-party, all-annoyances-smoothed-over LSP support would be an amazing product.

I paid for it (and merge) even after I started using neovim full time, because I used it for years to learn to code before I got a paid job. Their license terms were kind enough to let me do that, so I honored the spirit of it and paid them once I got paid.

If you had to, you could go from typescript to JavaScript overnight in a large project, whereas no similar escape hatch exists for C#.

As for the frontend, you have to have so JavaScript somewhere, it’s unavoidable, so typescript is just a way to make the inevitable more palatable.

I think it’s a lot like Excel and databases; in a way excel is often used as a sort of a “no-code” database.

There will always be use cases for the real thing, and there will always be people who reach for the easy option, and a lot of them really only need the easy option.

But there will also always be organizations who reach for the easy option, wildly outgrow it, and pay the price…

Depends on where you are, in a lot of the world a new sim is a few dollars from any convenience store on every corner, whereas I have no idea where I’d have to go to even talk to someone about an eSIM.

React is a little bit painful and massive overkill for web forms actually (compared to other approaches).

It’s the fighting with it that’s the issue; my experience is that a lot of devs go in to “force this stupid framework to work” mode and blow up tasks that should be 10 lines of code with no edge cases into 50 or 100 which “mostly works, good enough.”

React is by far the most adopted framework for desktop-level or near-desktop-level web applications.

That’s not totally true though. React, used correctly, lets you use and share a mental model where you have clearly defined the minimum complete information required to display any state of the app, and separately you have a set of simple functions which reliably convert pieces of that data to correct html.

That’s insanely powerful and massively reduces complexity in highly interactive apps, because it means you no longer need to think about “user did this, update this here now, and here and here” chains, and can just do “user did this, update the state” and have that state update render potentially hundreds of changes across the app without needing to do additional implementation.

But if you aren’t disciplined with maintaining, or don’t understand the difference between pure functions and side effects, and fall back to hacks to try to “make things render” or “stop wasting render cycles” you’ll end up with even more complexity than necessary.

Using react as another version of `getElementById` leads to a horrible mess much worse than writing vanilla javascript, and most people who have that complaint are doing it to themselves by fighting react either unintentionally or on purpose to show how it can be bad when abused.

Raw HTML and CSS is much easier to understand, and mandatory to understand because at the end of the day creating HTML and CSS is the only goal, but higher level abstractions can be super useful to manage complex projects, and the mental models and abstractions are the actual benefit.