edderly

Interoperability would mean you have a meaningful protocol encoded within JSON. JSON itself offers little value.

Yeah, a common stupid requirement. Perhaps a selling point for any solution would be to deploy a common serialization/de-serialization package that can be used on both the cloud and end point side.

If memory is a concern why are you trying to send JSON to a memory limited device?

No, not particularly. What I find amusing about Katsu is it reminds of the 1970s curry in a packet type of meal for example https://nostalgiacentral.com/pop-culture/food-drink/vesta-cu.... Also school dinners where a curry sauce would have a random sultana and a bit of carrot in it. Wonderfully disgusting.

Certainly chicken is increasingly popular, fish and chips is almost a boutique food these days since fish is expensive and also very easy to make badly. Whereas chicken is cheaper and easier https://archive.is/Mu1DL

Wouldn't it be a problem for Nest devices running on Fuchsia OS to get the hardware support they need? Most companies building consumer electronics products rely on hardware vendors to provide working kernels, drivers, etc. Speculatively, if you were able to leverage Android/Linux hardware support without the overhead of the rest of the Android OS, that would free up Nest from having to handle that problem.

If you're new to this area, I would first start by understanding which profiling tools you can use depending on the OS, languages and systems involved.

Even if your system is not C++, I've always enjoyed this talk and the subsequent discussion which tackles some of the problems associated with some programming practices and the impact on performance.

CppCon 2014: Mike Acton 'Data-Oriented Design and C++' https://youtu.be/rX0ItVEVjHc

If it helps I think you're right to take this approach.

In my experience defining error as 'handled' or handleable in code can often not be particularly helpful. Are the values from errno(3) always considered as handled?

EINVAL is almost always in "your" terms a fault, ENOSPC or EPIPE likely could only be handled as complete failures.

What I see too often is code which which propagates

The best product manager I worked with was just an exceptionally bright person, they were able to understand complexity of implementation (and even have a reasonable chance of doing it themselves) vs understanding the business need. Just basically a value add to the company without being an engineering manager.

Unfortunately most product managers are just people who sit in the role. They are just gatekeepers who take either credit or blame. They often have little skin in the game.

Overall, if you have a product management organisation, you're doing it wrong.

Since I only use reddit logged in and having the user preference set to the old UI, the most effective way for me to go cold turkey is to logout. Any twitch response to back to reddit presents the newer layout and I'm instantly compelled to close the browser tab again.

In my opinion, it always helps if you get to know the people reviewing your work personally. Sometimes, this happens naturally. You don't have to be buddies; however, if you understand a person's background, biases, and experience, it adds a lot of context to anything they say.

This is all over the US media, there's no engineering content here yet, just a disaster.

This is quite ghoulish and fits into the latter category IMO.

https://news.ycombinator.com/newsguidelines.html

What to Submit On-Topic: Anything that good hackers would find interesting. That includes more than hacking and startups. If you had to reduce it to a sentence, the answer might be: anything that gratifies one's intellectual curiosity.

Off-Topic: Most stories about politics, or crime, or sports, unless they're evidence of some interesting new phenomenon. Videos of pratfalls or disasters, or cute animal pictures. If they'd cover it on TV news, it's probably off-topic.

This has no place on HN

Indeed. So imagine doing performance profiling on a 90s UI framework from Psion and then getting feedback from S60 three months later after an integration cycle that you have a core perf or latency problem.

Does anyone know what license this is under?

Oh look qemu too https://github.com/SymbianSource/oss.FCL.sf.adapt.Qemu

https://github.com/SymbianSource/oss.FCL.sf.adapt.Qemu/blob/...

I'd try to build a textshell image, maybe the emulator or the beagleboard https://github.com/SymbianSource/oss.FCL.sf.adapt.beagleboar...

No, the OS was a mess. The UI split was the root of the nightmare.

Nokia were "running" (perhaps should read ruining) Symbian well before they bought it. They were only one of the four or was it five co-owners, but they ran rings around the others when pressuring Symbian leadership. They were the only phone manufacturer with a dedicated product support org, and their pre-prod devices were available in core engineering teams unlike Moto et al. Nokia were the key players to create a Symbian OS core without a coherent UI (Techview lol), no TCP/IP stack, no telephony stack. They helped reduce Symbian OS to swiss cheese because they were so concerned with with recouping their investment from gen 1 SOS products and terrified their competitors at the time got a tiny leg up.

I think it'll be fine. You don't need 7000 people to run a micro blogging service. It's really that simple.

I suspect you're over indexing on what what a person being stalked would do with code. The source code is a tool, and it can become clear to people outside of the corporate interests what the security model or lack thereof is.

I'm curious whether you think there is any benefit for tracking technology to be proprietary.

The obvious first thought is that any implementation for tracking should be open source and be backed by a publicly available standard.

Sorry, I've never heard of such a decorum or rule in London and I've lived there or around for 25 years. Not that I would go out of my way to have with a conversation with a cabbie, i prefer to mind my own business.

Not sure about the fraudsters necessarily, but it seems like a core irony of the so called web3 is that the concepts involved could have great utility for governance of individuals and companies in an economy where a great deal of effort is spent tracking down tax dodgers. However, the web3 anti-establishment shtick seems to sell better at the moment.

You do realize that Ayrton's nephew drove for Williams?

https://www.reuters.com/article/uk-motor-racing-williams-sen...

One Ring / Police program I am aware of provides cameras to victims of domestic violence when they find a new home. A common issue is that the abusive former partners try to find out where they live and often succeed. So answering the front door is in of itself a terrifying experience. So are they against 'that'?

So that appears to imply that in largely more wealthy cities are sending homeless people to less expensive cities and SF has an active program which is doing this too.

That is interesting and very concerning but that is 10 people when the homeless population in CA is 151,278 https://worldpopulationreview.com/state-rankings/homeless-po...

Thank you, is there a link where I could cite that information?

Who came up with the hypothesis that California is the dumping ground for the nation's homeless? I'd like to know if it stands up to scrutiny.

California itself has a population which is the size of a medium sized European country. It is large enough to have a sizable homeless population. If you are homeless are your chances of getting food and services better in the central valley or in SF? Also, are there significantly less homeless people on the East coast by comparison?

Thank you, this is what I was looking for.