I don't hold the in browser POC at fault for the trained model (but am amused by the efficacy of the model).
157 karma · joined April 20, 2015
I don't hold the in browser POC at fault for the trained model (but am amused by the efficacy of the model).
I think the key thing is it's not a need. What you are doing is fine if your team can hire the talent they need to maintain (and grow) the product/software to match the companies needs.
OCI standards (what Docker uses) to some extent are trying to make a uniform ecosystem so engineers and architects know what to expect before digging into a project. That should not be compulsory though; other systems that work only make 'bigger' systems from places like the open container initiative better by showing what works in the wild.
I'm sure the intent of their statement is salt/SMR/other exotic designs that the NRC has not greenlit (and, I think I'm ok NOT greenlighting designs that don't account for 50 - 80 years of maintenance/operation/risk)
I don't think technology and invention (or discovery for that matter) are synonymous. There has been progress in nuclear technology, even if it's so far non viable.
Conversation threads on hn are also nice in my opinion, they are not compulsory, if you forget a discussion was happening the platform allows that. Instead of throwing it back in your face to encourage engagement.
At any rate though, based on Intel's track record I think this content is still relevant and of value to engineers who don't have domain knowledge in compilers or work downstream.
Edit: I appreciate a response regardless. If I get an overwhelming amount of apathy in these responses that might just be a sign I should change my mind about the position.
I recognize what you are calling out/that performance will be the same on some workloads if you distribute or not. I would just point out less manufacturing causes less e-waste/I would rather live in a world where Nvidia sells 50 million 10*0 cards, than 500 million 1030 cards to create the same amount of compute in the world. It's not just the power costs to consider (but it could be there is a reality where running 500 million 1030s for their lifetime wastes so much less power, that the manufacturing costs to the planet are worth it).
I'm just ready to give my money to someone who wants to build on openXR, has a vr window manager in development, and the chops to build ambitious hardware (on Linux).
https://discord.com/channels/603723949586644997/603723949586...
Re (software) development: Yes it will need funding, but it's there right now https://github.com/SimulaVR/Simula and is agnostic/works with any openXR headset.
If you want to see a product that is open end to end and is not part of an ecosystem selling your information, then it has to be funded.
I realize most of the people reading this don't want a moral argument for spending $2k-$4k on a HMD, but thats what I am offering.
We should have multiple openXR compatible headsets to choose from, and specialized window managers that 'just work' in VR. Fund the FOSS projects you want to see in the world so others will follow.
It showed they couldn't communicate well, couldn't work in stealth mode, couldn't focus on building/proving out the mvp.
Other factors are just hindsight/observing them the decade after. Two of those factors might be. 1. Repeatedly quitting contracts (if it's not a good fit fine, if it's never a good fit maybe you're missing skills to complete a project).
2. Comments/behaviors that illustrated they would have been a poor manager if we scaled/inability to be wrong.
For me, other developers and contributors have been one of the most important factors for success/completing projects/keeping clients (in the contracting space). So I consider this an important lesson I was fortunate to learn early. I don't know who I would be working with now if I had failed to keep great talent around me (or for that matter, what skills I would not have developed).
I brought one person in to work on that with me, they proceeded to buy a domain for the top product name we were considering (canitake.com) within the first day. It was wonderful to get that red flag so soon, I stopped working with them, and abandoned the project. Losing the project was a little unfortunate, the data brought good questions someone might want to ask their doctor about; but knowing what I know now about "doing your own research" a lot of people would not have used this as a way to prepare to talk to a professional and would have interpreted the data themselves.
Not working with that acquaintance again was invaluable, they burned their way through the industry for the next decade. They could have messed up projects I actually cared about.
I'm well into worried this is another eve laptop / failed to deliver a real product situation.
So even if they are not sold out, Purism is not getting any money from me until I hear of delivered products to people I know.
If I block infinitedata-pa.gogleapis.com, maps will not function, but google maps will continue to collect telemetry data on my phone if it is running and has permissions. It will save that collected data until a user unblocks essential monitoring in order to use maps (Unless the user clears cache/data, or uninstalls maps, before unblocking).
That is the case I am pointing out, tc is a stopgap (and a welcome/useful one) but it does _not_ provide users a way to prevent _collecting_ of telemetry data to be sent off the device. It just delays the sending until the applications use is more valuable than the users privacy.
Edit: Things that could help with that:
1. Physical kill switches for radios (I know, that's not going to happen from any major arm cpu maker, the SOC is integrated, but it's the most practical solution.).
2. Granular permissions settings for androids network location provider. As an example, A permission that if app is running in the background send spoofed location data back (Once again, it's not that simple telemetry data is coming from many sources, I'm just listing what solves the problem.).