> the notion that it lacks nuance to describe the intricacies of text rendering
I took this to mean that any non-domain-specific language may be bad at describing that domain, e.g. why physicists, mathematicians, chemists, etc. have a common symbology for the discipline, or why programming languages exist. i.e., not so much that English is uniquely bad among written human language for conveying these topics, but just that any non-specialized language may be.
Though, I think the author did a fair job, but I lack the domain experience to guess at where the misconceptions might lie.
They linked a whole article detailing the complexities of specifically NAT traversal.
I should think it obvious that by removing an entire leaky layer of abstraction the process would be much simpler. Yes, you still need a coordination server, but instead of having to deduce the incoming/outgoing port mappings you can just share the "external IP" of each client--which in the IPV6 case isn't "external," it's just "the IP".
>Also NAT is a pretty simple abstraction, it's literally a single table.
...And now, let's try punching a hole through this "simple" table. Oops, someone is using a port-restricted or symmetric NAT and hole punching has gotten just a tad more complicated.
Running a firewall with upnp enabled has always amused me. Might as well just turn the firewall off if you let any machine shoot any hole it wants in it.
Anyone know if it's possible to bandwidth-limit the sync operations? I'd love to set up garage instances across my families' houses to act as a distributed backup, but I don't want to hose their (or my) down/uplink during awake hours. Having redundant selfhosted S3like storage would solve many problems for me, but I really need that capability.
> Initially, we experimented by building this as an app on Pebble, since it has a mic and I’m always wearing one. But, I realized quickly that this was suboptimal - it required me to use my other hand to press the button to start recording (lift-to-wake gestures and wake-words are too unreliable). This was tough to use while bicycling or carrying stuff.
I’ve never had that issue with my Apple Watch. Granted, apple are a world-class developer (arguably), so their stuff might be more reliable, but I use raise-to-speak and hey siri with my watch all the time.
This is probably also part of the reason that the AW battery lasts so much less time. It's always on the lookout for these events, and over time that ends up having a non-trivial impact on battery. For Pebble users, that would significantly compromise one of the main selling points of the Pebble.
But you have to instruct Siri to record/transcribe/save what you want to say; this does it automatically. It removes friction if you just want to record short notes.
I almost never want to take a note though, I usually want to perform an action.
Recording a note isn’t high friction in my opinion though: “Hey siri make a note XYZ”. Admittedly I don’t create or use notes like this, but I use reminders a lot and I’ve never felt like there was friction: “hey siri remind me to call Dave when I get home”
I do this too, the biggest issue I have is when the shitty voice to text doesn’t get it right, and I look at my shopping list the next day wondering wtf an “ear pig” is.
I feel there may still be a way solve it using existing hardware -- rather than go build entirely new hardware for it.
Some low effort ideas I cna think of -- a wake word instead of button press; a flick of the wrist; or maybe press the watch to your chin; There must a few more elegant solutions possible if smarter people put their minds to it.
Pixel watch is an order of magnitude more powerful and expensive than a Pebble though. Raise to wake is not as simple as it may seem considering most big brand smart watches didn't have a decently working implementation of it until only recently. It seems like the author wanted to keep it within the Pebble realm.
The pixel watch can be a nightmare. I've had the version 1 and the version 2 for years and I gave up because of the bugs. Random crashing, randomly dialing 911, just weird stuff that should not happen.
And then there's the support which is zero support. Completely frustrating to post a message and then get some volunteer support Tech, hahaha, saying expect improvements! And it's a volunteer saying that. And they have no authority. And There is no support, it all falls through. Random crashing on both versions of the watch. The first version screen was flickering like an old school television trying to tune in a distant UHF broadcast. Display drivers anyone?
So, pixel watches are in the drawer and I've got a Garmin watch on right now. Garmin is clunky but at least it's reliably clunky.
So it feels like a mis comparison, to me who's had the pixel watches.
I used to own the pebble, a couple versions of it, when they were first announced for several years again. And I found them to be very reliable and lightweight and usable.
I wanted a smartwatch that could talk to Google's home ecosystem and so I traded out of Pebble. And it's just been kind of mediocre misery.
Plus I don't know what Google is doing but recharging the pixel watch every 18 hours, or 36 if you're super lucky and your apps on the pixel watch behave themselves correctly, makes me feel like a slave to Google's naive product manager aspirations.
Like, "it can do everything, and we make money off of you because you are the product!" While at the same time making me miserable.
Economics don't work like that though. Google has the benefits of economies of scale and stable manufacturing partnerships, not to mention probably a lot more of the watch parts are designed in-house. I'd be surprised if Pebble could achieve anything close to the Pixel hardware for even twice the price.
It seems like Pebble is focusing on a niche market and this new product seems completely in line with that. There are plenty of other companies targeting the common folk who have no desire to optimize their life like this.
Niche market seems like an exaggeration, because they're competing against literal monopolies.
Pebble serves those people who want to watch or a ring that doesn't require being a slave to a wall wart, who want the watch to last for a long time. Take a look at Garmin, they do that too and they are a successful company. They are much older than Google and they still have a hard time keeping up with Google and it's billions of dollars of of mystery money advertising revenue.
The pixel hardware is a battery draining nightmare, in my personal experience having pixel watches for years and being a long-term pixel phone user. Even today the pixel phone that I have, after having I think five of these things, drains battery probably 20 to 40% faster than .. the competitor that I would next buy if I weren't feeling like I wanted some of the features that Google has bundled in with their phone and home and other like mnvo and messaging products. So, it seems like a mis comparison there, in my opinion. I don't want a smartwatch that lasts 25 hours and then has to be recharged. Or a smartwatch where the screen turns into a UHF channel just going out of tune and there's no tech support on Earth literally that is willing to help me. Volunteers on Google's support forums are lying to themselves that they have any power or sway with Google. It's a waste of time in my experience.
Man, I wish this was true. I've given the same feedback on a colleague's clearly LLM-generated PRs. Initially I put effort into explaining why I was flagging the issues, now I just tag them with a sadface and my colleague replies "oh, cursor forgot." Clearly he isn't reading the PRs before they make it to me; so long as it's past lint and our test suite he just sends the PR.
I'd worry less if the LLMs weren't prone to modifying the preconditions of the test whenever they fail such that the tests get neutered, rather than correctly resolving the logic issues.
We need to develop new etiquette around submitting AI-generated code for review. Using AI for code generation is one thing, but asking other people review something that you neither wrote nor read is inconsiderate of their time.
I'm getting AI generated product requirements that they haven't read themselves. It is so frustrating. Random requirements like "this service must have a response time of 5s or less" - "A retry mechanism must be present". We have a specific SLA already for response time and the designs don't have a retry mechanism built.
The bad product managers have become 10x worse because they just generate AI garbage to spray at the engineering team. We are now writing AI review process for our user stories to counter the AI generation of the product team. I'd much rather spend my time building things than having AI wars between teams.
Oof. My general principle is "sending AI-authored prose to another human without at least editing it is rude". Getting an AI-generated message from someone at all feels rude to me, kind of like an extreme version of "dictated but not read" being in a letter in the old days.
At least they're running the test suite? I'm working with guys who don't even do that! I've also heard "I've fixed the tests" only to discover, yes, the tests pass now, but the behavior is no longer correct...
I learned recently our company has an informal policy to discourage hiring fresh grads, which would explain why I haven't seen any hires at the bottom of our grading scale. I'm one step above (though arguably I could be two up by experience, I misplayed my negotiations), but I kinda feel like I'm dangling off the edge.
Until it isn't because enough people realize it is inherently flawed and will never result in stability and they would rather die than relegate themselves, their children, and all their later generations, to indefinite servitude of an outdated economic system. Provided we don't kill our world first in our pursuit of endless profit growth.
> I'd much rather deal with some less stability and have a lot more resources
This strategy works so long as you're in the group of people who do indeed have "more resources," but breaks down if you're marginalized in any way, or if you don't want to support the exploitative system.
That is what people always says about their current culture or economy or political system, even as they are on the very edge of systemic change. And quite frankly to me that just reads like an excuse to not do or try anything so people can kick the can down the road, benefiting themselves at the expense of many others both currently and in the future as things deteriorate further.
it is if that's all people do, but I think it is a necessary step to realize that we do live under a system that encourages an amoral allocation of resources. If people only ever shrug that off or treat it as intractable it will never change. Some would argue that it cannot be changed, but I think that just means they haven't read history.
reply