Had a newer version at my local library and got me interested in computer hardware in Middle School years.
1,987 karma · joined January 26, 2013
Had a newer version at my local library and got me interested in computer hardware in Middle School years.
Anyone tried it out yet, how does it look so far?
Brokers reselling my health info is far more critical to me than my buying habits.
Is there a "do not sell my health info" checkbox?
Maybe we'll have a renaissance like what Satya did to Microsoft...
Basic screen sharing does work as you said.
I'd also try the new Black Mesa remake, it's really well done.
The article is light on specifics but this stood out to me, most Tesla's take longer to charge. I'd imagine an aircraft would need more power than a Tesla, so how are they transferring energy so fast that automobiles can't do it but aircraft can?
Originally, IBM's East-Fishkill plant was the largest trusted-foundry of near latest generations (14nm, 22nm) but that was sold off to Global-Foundries, which then sold it off to ON Semiconductor. Now it needs someone to fab the latest generation with a full chain-of-trust.
[1] https://semiengineering.com/a-crisis-in-dods-trusted-foundry...
[2]https://www.dau.edu/cop/dmsms/DAU%20Sponsored%20Documents/Ou...
tar -I zstd -xvf archive.tar.zst
https://stackoverflow.com/questions/45355277/how-can-i-decom...Hopefully there's another option added to tar that simplifies this if this compression becomes mainstream.
It'll live forever...
/s
Play on a loop... Nice white-noise generator :)
>Kick butt, have fun, don’t cheat, love our customers, change computing forever
Here we have Boeing, a company built by engineers with the engineering ethos, and MBA types were given the helm of the company. Why didn't the culture fit apply to new leadership?
Just wanted to clarify that running Cassandra & Kafka on Mesos is much easier now with the DC/OS Commons SDK.[1] Spark has always been supported on Mesos.[2]
[1]https://github.com/mesosphere/dcos-commons
Cassandra:https://docs.d2iq.com/mesosphere/dcos/services/cassandra/2.7...
Kafka:https://docs.d2iq.com/mesosphere/dcos/services/kafka/2.8.0-2...
[2]https://docs.d2iq.com/mesosphere/dcos/services/spark/2.9.0-2...
- Ownership of IP: IP produced in your own time on your own equipment doesn't belong to your employer.
- Non-competes: Not enforceable in CA
- Access to capital: Plenty in CA.
I'd say the first two points are what differentiate Silicon Valley from the rest of the tech capitals.
I'd recommend starting with an academic operating system to nail the fundamentals down, once you have a solid foundation you can then use all the excellent links provided by everyone else and ramp up on production grade kernels.
I have linked to multiple course syllabus'es below from excellent institutes, pick whichever feels most comfortable.
Harvard with MIPS based OS/161 (I learned this personally): http://www.eecs.harvard.edu/~cs161/syllabus.html
Berkeley EECS 162 (John Kubiatowicz is amazing and is behind RISC V) https://inst.eecs.berkeley.edu/~cs162/sp19/
MIT OCW: https://ocw.mit.edu/courses/electrical-engineering-and-compu...
I've read that the oceans end up absorbing majority of the CO2 emitted, if that's the case, I haven't seen anything (to my knowledge) that goes towards accelerating this in a sustained way for the marine ecosystem.
The oceans are far larger and I suspect will have less issues with rolling out methods of coping with CO2 i.e won't disrupt jobs or or ways of life.
Does it make sense to attack the problem that way? It has the potential to scale much more quickly. Is there a company attacking this sorts of issues like SolarCity?
Mitsubishi is making a few moves [1], it recently acquired CRJ from Bombardier.
[1] https://asia.nikkei.com/Business/Company-in-focus/Mitsubishi...
1. No prototypes. Just make the game. Polish as you go. Don't depend on polish happening later. Always maintain constantly shippable code. (Large teams require more planning though.)
2. It's incredibly important that your game can always be run by your team. Bulletproof your engine by providing defaults (for input data) upon load failure.
3. Keep your code absolutely simple. Keep looking at your functions and figure out how you can simplify further.
4. Great tools help make great games. Spend as much time on tools as possible.
5. We are our own best testing team and should never allow anyone else to experience bugs or see the game crash. Don't waste others' time. Test thoroughly before checking in your code.
6. As soon as you see a bug, you fix it. Do not continue on. If you don't fix your bugs your new code will be built on a buggy codebase and ensure an unstable foundation.
7. Use a development system that is superior to your target.
8. Write your code for this game only - not for a future game. You're going to be writing new code later because you'll be smarter.
9. Encapsulate functionality to ensure design consistency. This minimizes mistakes and saves design time.
10. Try to code transparently. Tell your lead and peers exactly how you are going to solve your current task and get feedback and advice. Do not treat game programming like each coder is a black box. The project could go off the rails and cause delays.
11. Programming is a creative art form based in logic. Every programmer is different and will code differently. It's the output that matters.
Extra advice:
1. Only program for a few minutes and test code immediately. Try not to code for even as long as 30 minutes. This is will help to avoid debugging because you will catch bugs sooner, and won't have as wide an area of code to look through for the bug.
I'm not enthused about supporting anything that worsens the global climate crisis and its irresponsible of large companies to support cryptocurrencies with its terrible power usage right now.
I spent atlot of time on MS Flight Simulator, from ver 5.1 for DOS all the way up to FSX.
It was a sad day when MS discontinued the product as it is the oldest product offered by the company.
This really feels like a renaissance at Microsoft as the hardcore audience (simmers) for this is small and presumably lead to the earlier cancellation.
Looking forward to the release!