4,891 karma · joined October 27, 2013
But, I do not think it's reasonable for an automated system to systematically capture, store, and analyze all of my movements (or anyone else who is not suspected of a serious crime). If they suspect I have done something illegal, they should have to get a warrant and then the system can be triggered to start tracking me.
I understand the desire for the data... sometimes I would like to know if my kids are following the rules at home, but I have a stronger conviction that I don't want my kids to grow up in a home where they feel like they are under constant surveillance. It's a gross feeling to be under constant surveillance, like you're living in a panopticon built for prisoners, which is an unfair side effect when you've done nothing wrong. Mass data surveillance of everyone is a totalitarian dystopian that I don't want to live in.
Reminds me of a guy near me who bought three already massive adjacent properties. Tore down two of them. One become a pond. The other one was rebuilt into a massive $30M mansion. The third was already a $15M mansion so he kept that as his guest house. The funny thing is that his guest house... has a guest house.
https://www.cdotrends.com/story/3823/groq-ai-chip-delivers-b...
I see good use cases for building entirely in html/JS and also building entirely in WASM.
I can't speak for OP but I can report on what I'm seeing... I know a lot of British, Canadian, and Australian expats that have moved to California in the past 5-15 years.
Why? Healthcare is probably everyone's first concern, but expats tend to be well educated successful people who can afford excellent healthcare... I'm an expat from a different country and seeing the top end of the healthcare facilities in the States is a luxury experience compared to national healthcare where I'm from. I wish everyone here had access to that, but at least poor people in California do have access to state healthcare.
Politics is a shit show, and has gotten worse recently of course, but that's true in a lot of places now and everyone I know came in before the most recent decline. I know a couple of families who have gone back to their countries, but all of them went back because they wanted to be close to family again, but none of them left because they didn't like it here.
Across everyone I know, the main appeals for coming to California seem to be weather and lower taxes than their home country. Cost of living is similar to many of the big cities in the countries I mentioned above. I'm not suggesting America is a better place, that's a different calculation for everyone, just reporting on what I'm seeing.
A newcomer in the heavy equipment space will have similar challenges and advantages. Funny enough, a lot of heavy equipment works very similar to cars with their CAN (and other) Buses for control and feedback.
Ya, I'd pay $0.25 or $0.50 on a whim for any random article. For good articles I'd pay more, but the problem is that you don't know if it's going to be good information or some clickbait crap until you read it, so it has to be priced with that risk in mind.
But maybe I'm unique, I currently have paid subscriptions to a few online publications because I believe it's important to pay for news with money instead of clicks (if you want the news provider to be incentivized to generate quality news instead of clickthroughs).
https://issuetracker.google.com/issues/362210027?pli=1
You can add a recurring ping/pong between the client/server so you can know with some recency that the connection has been lost. You shouldn't have to do that, but you probably want to until this bug is fixed.
Chrome no longer fires Close or Error events when a websocket disconnects (well, at least not when they happen, they get fired about 10 minutes later!). So, your application won't know for 10 minutes that the connection has been severed (unless the internet connection is also lost, but that isn't always the case when a websocket is disconnected).
Here's the chrome bug:
https://issuetracker.google.com/issues/362210027?pli=1
From that bug report it looks like the Chrome bug is less than a year old, but the Chrome bug is originally mentioned here in April 2023 for a similar bug in iOS (the iOS bug has been resolved):
https://stackoverflow.com/questions/75869629/ios-websocket-c...
I kind of suspect Chrome is actually doing this intentionally. I believe they do this so a tab can recover from background sleep without firing a websocket close event. That's helpful in some cases, but it's a disaster in other cases, and it doesn't matter either way... it breaks the specification for how websockets are expected to work. WebSockets should always fire Close and Error events immediately when they occur.