zurn

Looks like the BeBox motherboard didn't have the external L2 in the first place.

Besides web sources, logic dictates this as well: Since dual-cpu was its selling point, it wouldn't make sense to ship a disabled L2 implementaton on the mobo at extra cost. There was no single-cpu model.

The Android version doesn't seem to be.

Does this use case involve US data transfer? Azure seems to have invested quite a lot into implementing EU data residency.

> > Machine -> Asm -> C -> Python -> LLM (Human language)

> Something that you neglected to mention is, with every abstraction layer up to Python, everything is predictable and repeatable.

As long as you consider C and dragons flying out of your nose predictable.

(Insert similar quip about hardware)

But in SDR, the "underlying technology" of radio modulation, spread spectrum, etc is your software, no?

Electricity is fungible, so when big operators buy wind-only power from the market, the rest of the demand uses the non-green power left in the pool.

(It still potentially increases wind buildout so it can have indirect positive impact especially if wind is not competitive at the same prices with fossils)

Also the accounting is "we bought as many MWh of wind power as we used" over some time window, so in reality they are using fossil power in peaks, competing with everyone else and placing pressure to expand fossil based capacity.

These are also the reasons it's probably better to talk about the electricity used instead of trying to translate it to emissions by proxy, which is prone to being gamed due to abovementioned reasons.

(Also the number is high rather than low if you consider that all the individual slices of the emisison pie at this subdivision granularity are pretty small)

There are some YAML based schemas there too. How does this work, is there a canonical YAML->JSON transformation, or does JSON schema spec have explicit YAML support?

edit: skipping the theoretical foundations, there seems to be at least this tool that claims to validate yaml against json schema: https://github.com/json-schema-everywhere/pajv

You're allowed only very fractional duty cycle access. So depends on what you mean by "alternative to internet", but generally no.

Software patentability is limited in a lot of places, can this actually be an argument in favour of doing things using SDR?

Buildings lose value over time in most places. And in many places where they don't, including renovation investments in the picture results shows declining value.

How does the AGPL apply in this case, does it apply to the apps you build?

Doesn't the shielding help prevent heat output only with short duration power use peaks? If we imagine the conductor is heating at the same rate 24/7, all of the heat must flow out of the cable at the same rate it's getting generated unless the conductor's temperature can increase indefinitely.

Unsurprisingly AWS is ghetto about this.

The x86 monoculture has shaken around a bit. But surprisingly it seems there has been friction even on the JVM side, partly because of Docker style nonportable containers had time to cement in the x86 monoculture period.

Unikernels are here today.

The other way to eliminate protection boundary crossings is to push everything to userspace, a la Snabb, DPDK etc.

We're so far behind in replacing fossils and fighting off global warming disaster, that we should do both. Nuclear has worse bang for the buck though and decades long lead times. But as long as it can be financed without displacing more capital efficient renewables we should still build nuclear as well.

Network segregation is your last line of defense. Having anything rely on it is a recipe for a bad security that's always just one step away from someone getting around it due to misconfiguration, request forgery, networks configuration changes over time, malware transiting over via VPNs etc. And of course from the SW vendor POV they don't know if the customer env employs this defense in depth layer, so it's really irresponsible to rely on it. Like is amply demonstrated here...

If a product upon unboxing promptly flops on its back with "come here internet" access controls, even if by good fortune it's saved by your network ACLs, it's time to put it back in the box and return it.

Interesting that ES is still such a widely used component, this is a huge red flag about a software product. And of course there are lots of other regular complaints about it (eg uses a lot of memory and wants a 3-node cluster so costs 4 figures/mo to run on AWS).

Your impressions are cordect: DynamoDB is quite low-level and more like a DB kit than ready to use DB, for most applications it's better to use something else.

There are benchmarks for different purpouses, but for users if you're going to run just one benchmark, the best one is the workload you have, or anticipate.

Looked up the release date for this phone: January 2021.

S8 was released in 2017, for anyone else curious.

We do. Follow some of the Three.js people in Twitter to see some interesting things people are making, eg https://twitter.com/mrdoob

For example this IFC-in-browser thing looks amazingly useful: https://twitter.com/ifc_js/status/1462880392915083269

I just went through comments from all the times this has been reposted in the past 10 years, and this is (so far) the first time there aren't any complaints about not working in their browser! I'm counting just the submissions that got >10 comments.

The previous time, from 2017[1], was already quite good - there was only a single complaint, and that was about someone missing a WebGL extension this needs for floating point textures.

[1] https://news.ycombinator.com/item?id=14432809

Seems like a possibly good business strategy for w3techs.

They publish numbers that are very surprising to most people, like Python and JS are used on 1.5% of sites vs PHP on 79%, then offer some very handwavy text about the data ("In order to obtain any information from websites, we rely on the websites themselves"), and then offer a full report for $$$ where they probably more fully own up to how they come up with this clearly flawed data.

In the end the paying customer sees the shortcomings of the data, feels relieved that their assumptions weren't invalidated and has invested some money to doing due diligence.

People living in arctic areas with multi-month polar night generally already have some other heating energy source, as it gets a bit chilly. But in the summer they can have 24/7 solar energy!

There's not many people living in these areas though like the sibling comment points out.

Many of the loads discussed, eg washing machines, are also reasonable matches a local solar power source, as it's much cheaper to buffer hot water than have large batteries.

(Water heating dominates the energy used in those, the mechanical sloshing around takes trivial power compared to it).

Actually i misread the example as using println instead of str because my brain had been primed by println in the headline!

For those of us using CIDER don't forget #break / #dbg!

https://docs.cider.mx/cider/debugging/debugger.html#using-th...

Ok. So the P4 language is not competing with it, and could be made to compile to ebpf.