I assume that by "get them out" the parent meant "move your crypto from an exchange to a wallet you control". If your end goal is to be out of crypto altogether it would make far more sense to just sell while the exchanges are still open.
> If you have assets in an un-audited exchange, get them out now.
This is Mexican standoff. The only "value" crypto assets have comes from exchanges that will trade them for fiat. If crypto holders stop trusting exchanges and pull all their assets that will cause the exchanges to fail and those assets will then be worth nothing. On the other side if exchanges try to earn the trust of holders by becoming "fully transparent" it will be revealed that there's not nearly enough fiat reserves to support the current valuations. (It does no good for Binance to prove they have a reserve of $18B of Tether to back the $18BN BUSD marketcap if turns out Tether is actually mostly backed by Bitcoin that only has a USD value because it can be traded for BUSD...)
Funding for NIF is 100% about weapons, it's never been about energy. After '97 (when Clinton signed the CTBT and the US agreed to stop testing new weapons) the national labs were in a panic until some clever DOE wonk invented the concept of "stockpile stewardship" and they went back to business more or less as usual.
Scientifically it's potentially very interesting: close up observation of what's going on in the center of a star and all that. I'd ignore all "the future of free clean energy is upon us at last!" hype. That's the lab and the government officials trying to drum up publicity that can then be milked for financial/political capital (it costs many billions to build and run a facility like this), coupled with lazy news outlets trying to milk sensationalist headlines for eyeballs.
Scaling the NIF's approach (laser inertial confinement) isn't about more reaction mass per pulse, it's about more frequent pulses, and is probably not going to be practical or cost effective in the foreseeable future. The fuel pellets are tiny (~2mm), their container is only about 1cm and must be nearly perfectly spherical. A continuous power plant would consume about half a million of them per day (6 per second), all of which need to be shot with perfect timing, precision, and reliability to the exact center of the laser sphere. My guess is magnetic systems are much more likely to ever be used in power generation.
My favorite so far was a company I founded about 20 years ago with a friend who worked in the film sound industry. He had an idea for a hyper-niche tool for automatically syncing changes from video to sound (industry term is "conforming"). He'd approached a couple people/companies he knew that made tools in adjacent spaces but got turned down with "that's impossible" or "it's not worth it". I had no experience in the space but I got intrigued just from a "can it be done" perspective and coded it up. Once written it required very little maintenance, it was just available on our website for download and we used a shareware service to deal with licensing and sales. Only marketing was word of mouth. Every time someone bought a copy the shareware service would send a text, so I set the text alert sound for their number to be the cash register sound. It was a small addressable market so didn't sell all that often but it was always a little dopamine boost to hear the "ka-ching" come out of my phone. Most sales only netted me a couple hundred bucks, but every once in a while a big player (like a movie studio) would pick up a bunch of copies at once. Eventually sold it off to a competitor and collected a small royalty stream for another few years.
Among its other endeavors, FTX created FTT, a token that had a peak notional market cap just under $10B, and that value seems to have been used to paper over massive holes in the FTX balance sheet. Massive, unexplained movements of FTT between FTX and Alameda Research[1] presaged the imminent collapse of both companies, and Binance dumping their FTT holdings was the precipitating event. FTX is about as "crypto" as you can get.
IMO of the three examples only the last one is a clear case of a company policy that can and should be followed even at the expense of productivity, and if their argument is really "how would anyone find out" you need to kick that up the management chain--this person could be putting your company at risk. For the other two your rationale is essentially "doing it the standard way makes the team more productive", but clearly comes at the cost of making this employee less productive, and your argument is empty--they are already seeking to be as productive as they think they can be. Assuming this person on net is more productive than average just assign someone else to backfill their unit tests and learn to live with the overly complex PRs.
Fear it happening or fear its consequences? Doxxing already happens all the time, but the main tools are things like account names or image search, this sort of tool could take it to a new level. A simple experiment would be to run this same algorithm against another site (say Twitter or Reddit) and see if it can reliably pick out the same peoples' accounts there. Once anyone on the internet can quickly/easily draw that sort of connection it would require incredible diligence to avoid de-anonimyzation while still maintaining any sort of "real self" presence on the internet. How much we should fear the consequences probably depends a lot on how marginalized you are within your society, but since just revealing your gender is enough to invite harassment in many forums I'm not optimistic.
I remember a few years ago some more dynamic presentation modes making a bit of a splash. I used one of them[1] to good reception in at least one talk, but ultimately it felt more like really slick slide-to-slide transitions than a fundamentally different paradigm.
Cloud providers aren't guessing at demand to plan capacity, they're literally building new data centers and then wheeling new racks into them as fast as they physically can (short-term decisions are more likely made at the other end, e.g. when to retire old systems, not add new ones). AWS was born out of the fact that Amazon's own compute needs are inherently variable so to meet peak demand they had to "over-provision" compared to average demand--this in turn meant they had a lot of excess compute power most of the time. At the point when Amazon still was a dominant consumer of AWS, spot instances were actually a deliberate convenience to Amazon, since it meant AWS could monetize resources while still ensuring Amazon could claim them instantly when needed (later they added a two minute warning, but early on they could literally disappear at any moment, and regularly did).
The value of their inventory is plummeting and those margins will continue to contract for however long it takes the last couple of bubble years to work their way through the system. Maybe the brand would survive a bankruptcy, but the equity definitely won't, and the bondholders are going to take a serious haircut too.
I was once pitched a startup by some Amazon vets whose elevator pitch was "Apollo for everyone". I literally laughed out loud, which was followed by some very awkward assurances from them that they were not, in fact, trying to be funny.
If you really want to write C just do it--most popular languages have a defined way to interface with C code, and if not you can almost always find a way to communicate with a C program via stdin/out. You can always justify to your teammates/bosses on "performance reasons" and they'll probably think you know some deep magic. (In practice most interpreters have gotten fast enough that it can be difficult to come out ahead after the overhead of going through an interface layer, but they might not know that.)
I think the path is more clearly thought of as HTML+CSS -> display list -> *. The display list is some abstract definition of what needs to be drawn by a renderer. In theory anything that fully describes all possible operations works, including bespoke things like SkPicture or general purpose graphical languages like SVG or PostScript. In practice there's never a single language that can describe everything, because display capabilities evolve and new operations are added all the time (e.g. advanced typography features for fonts). PDF can cover a really broad set of use cases, but it also wasn't designed as an intermediate format (it was closely tied to the PDF reader) so it's easier to get into than out of. SVG is possibly a better candidate, as it is already used effectively as an intermediate representation (e.g. D3.js "renders" to SVG).
The 80% less CO2 number is BS, since the claimed savings are only after "water boiling phase excluded". Guessing this is more like 10% overall, assuming you turn your stove down to a low boil after the pasta is in.
Here's the thing about being an engineer who isn't "dead weight": you can always find a new job. To keep that 5% (or 20% or whatever the real number is) of truly productive engineers you need to make the company a place they want to work. So sure most of the people playing ping pong in your lounge aren't really worth the cost of a ping pong ball much less their salary, but your star engineers maybe like playing ping pong too, and like having someone to play with.
Internet scale companies like Google happily embrace intellectual property laws when it's their IP on the line, they just don't care about anyone else's. And it's not an issue of "can't scale": Google's ad revenue is bigger than the entire GDP of Kentucky--they could literally hire 1% of the US population to work in fraud management and still turn a profit.
Ironically, despite the elaborate spec most participants will wind up just using an ad hoc convention of embedding critical information in non-semantic text fields (or "note segments") with bespoke codes & delimiters.
This guy should return the prize and apologize for deceiving the judges. The rules state:
"All items entered for the competition must be entered in the name of the person who created the entry."
If Allen had hired 100 humans to create images based on his prompt, and then submitted his favorite of those under his name I don't think anyone would consider that legitimate. IMO having Midjourney generate 100 images is no different: Allen did not "create" this art, it was created by Midjourney (and by proxy, by all of the artists it trained on).
AI that imitates well-known composers goes back much further, I remember attending a concert of "virtual mozart" works at UC Santa Cruz back in the late 80s/early 90s
It's kind of a trolley problem: I'm not "fine" with 480p, but also not fine with throwing away stuff that still works. That seems to mean the status quo wins until the thing stops working.
Nothing happened to them. Nothing ever happens to them! There's a now twenty year old Panasonic still hanging on my wall that refuses to stop working flawlessly and thus allow me to guiltlessly replace its 480 fat & smugly glowing rows of pixels with something a little more modern.
The real problem here is browsers treating recently "expired" (but otherwise still perfectly "valid") certificates as comparable in danger to visiting a known malware den. This is absolutely the sort of thing that could harmlessly wait until the next Monday to address if it weren't for the overwrought interstitial warning page.
Many years ago people (including me [1]) started using the Skipjack cipher for the purpose of obfuscating sequential numbers when they needed to be externalized (e.g. putting auto-incremented ids in urls). Since it was originally designed to encrypt media in realtime on 90s era silicon it's quite low overhead. I've often wondered if/when a database vendor would get around to building similar functionality directly into their engine since that would make the approach much more practical to adopt.
It's much like the difference between "how" and "what". SQL select statements are my favored example of declarative: you simply "declare" what you want ("all rows from this table with these values in those columns") and it's up to an engine to actually figure out how to do that for you. In an imperative language like C you could produce the same output, but you'd be specifying how, not just what: a for loop to iterate over each row in the table, if statements to compare values, etc.
I'm not worried about the ad supported free storage providers. On YouTube the ratio is something like 10,000 views for every 1 upload, so they amortize that storage cost across a lot of other users, not just the person who uploads it. Ratio will be lower on Facebook but even active users probably don't average more than 1 or 2 uploads per day. I've had the same gmail address for over 10 years, never delete anything, and I'm still under 50% of their free storage limit.
This headline is egregiously misleading clickbait, since it is based on an absurd and self contradictory hypothetical:
"If my product had 10,000 daily active users generating 100 events per day, I’d easily hit that size in less than a year ... If I built an application to visualize this result and refreshed it every second, I would spend $40,340.16/day on Tinybird’s Pro-plan"
There is no plausible business sense in refreshing the display of a year's worth of data every second, and even scaling back to a likely still-unreasonably-frequent refresh rate of once per hour you're down to just $11/day.