skysight-inc/HackerNews huggingface dataset:
Yes it was mostly heating with electricity, though I used a wood stove as well, but that's difficult to use efficiently - so it didn't help as much as I thought it would (w.r.t. saving electricity). No gas or oil. The only change was to install the heat pump, and boom - electricity usage way down. Now the biggest user is hot water (hot water tank for showers and washing). I save money by showering at the gym..
I still have the electric heaters installed in my living room - they haven't been used a single time since 2010. As they're permanent installations I haven't got them removed, or I would have.
It is on every persons phone, it is the defacto standard.
There was a big push about two years back by many people to change application when Whatsapp's privacy policy was changing and many pushed telegram and signal. The two or three of my friends, who left and held out, have now reinstalled Whatsapp. There's simply no easy way for them to speak to everyone else. People are reluctant to text and won't bother installing another application. (BTW this was in Africa.)
And also every article in this website:

https://ciechanow.ski/gps/
> If the employer won't listen, the usual thing to do is quit, start their own business, and outcompete them. There are lots of small business coffeeshops. They aren't terribly hard to get going.

After reading through all the comments in this thread, I'm of the opinion that Walter Bright isn't discussing this in good faith. Take his comment quoted above: starting a simple coffee shop requires capital anywhere from $80k - $250k (yes, I have researched this). No hourly wage worker or grouping of workers will have that kind of capital, nor access to it. Walter Bright has argued elsewhere that loans are a thing with a good business plan. Again - it's a bad faith argument because business plans do not fall from the sky - it takes time and knowledge to put one together and if we've learned one thing in America - hourly wage workers do not have time nor education to write one. And oh, Banks do not lend that kind of money simply based on a "business plan", they require collateral, which hourly wage workers do not have.

I call <cough> bee <cough> es on Walter Bright's arguments.
They also don't give units for the price of natural gas.
The benefit of Japan, Singapore, South Korea is that they are countries in Asia that have historically been supported by the West.

Practically, it means they enjoy easy access to Europe, North America, as well as Asia with little trouble.
The amount of "defensively [do something]" and "best practices" is another way of saying "this format is so bad you need to thread carefully or else we'll blame it on you".

Good format should not require defensive writing, and also "best practice" is a bit of misunderstanding: it's best practice to avoid such a bad format, not attempt to screw people into it and then blame them for not following some arbitrary set of rules.
>There's no reason that hardware should be designed to do unreasonable things just because that's "obeying its operator".

You're not talking about designing a piece of hardware to do unreasonable things. You're talking about designing a piece of hardware to be unable to do arbitrary things. Why do I say arbitrary? Because the designer is not omniscient. They cannot conceive of all the possible future situations in which their product will be used. Are you really unable to imagine situations where it might be necessary to drive on the road regardless of the conditions outside?

That aside, this has nothing to do with libertarianism or "doing whatever you want". I'm not saying if you decide to drive on the road in such conditions you should not be liable if you cause an accident. I'm saying, simply, "people should be able to use their property however they like". That doesn't seem like such a controversial idea to me. Or are you saying you shouldn't be able to do that? You don't trust yourself to use your property responsibly?
On the same system? I can see that. One thing I've lamented about XML for years is that it's a pain when moving to different systems that have their own namespaces/DTDs.
For a block that won't even grant a rocket launchpad permit, I'd say this timeline is probably optimistic.

If we look at how other permit processes have worked within our industry, it will be at least 10-15 years before we can actually begin mining and deliver raw materials to the market.
Having dealt with utf8mb4 data being inserted into the utf8mb3 columns many many times in the past, I've never had a table "instantly go down". You either get silent truncation or a refusal to insert the data.
The blurb above the table notes that the ranking is "the number of destinations their holders can access without a prior visa," and that it is based on data from IATA. Basically, the same data as used by airlines to assess documentation requirements before allowing passengers to board international flights.

The UK is above Belgium because, according to their data, a British passport allows visa free access to 187 destinations, while a Belgian passport only allows access to 186 destinations.

There's also a full methodology page at https://www.henleyglobal.com/passport-index/about
I think code comments and breaking everything into well-named functions, along with ample side documentation, make it fairly clear to follow. The business logic gets confusing - but anyone who had to work on the code would need to understand that first anyway. I don't think the code itself is difficult. It's all in the docs. Frankly, I don't always remember how something should work and I need to spend a few hours to re-understand some tricky piece of 10 year old code again before I change it. That's the job.

My main concern, of course, is not leaving a mess for myself. That should be every coder's priority. Then taking over someone else's projects wouldn't be so hard.
Why not just have no mappings and reuse the same objects?
> Json is so obvious that Douglas Crockford claims to have discovered it — not invented.

I mean, it's called "JavaScript Object Notation" for a reason. From what I know, the beginnings of it really were in the early days of AJAX: People were looking for a good way to encode complex data structures in dynamically generated script tags.

Then someone stumbled over essentially a random syntax element in JavaScript that turned out to be extremely well-suited for that task.

So I think talking about "discovering" JSON as a JS syntax feature which later became its own thing is quite correct here.
Every day we stray farther from the light of XML.

At this point, it’s just plain ridiculous.
I remember being excited when XML hit 1.0 (as a new programmer this seemed like a huge advance over things like classic Unix configuration files), and progressively disappointed over the next decade as the promise not only wasn’t delivered on.

The things which killed XML seem to me to be related to the old standards culture: the people involved assumed adoption was inevitable and distracted themselves with increasingly arcane thickets of new standards, with the assumption that someone else would spend time on the “boring” work of building professional-quality tools and documentation or cleaning up usability warts. That other 80% of the work never happened and most people who had a choice moved on.

As a thought experience, imagine if libxml2 had had even a single dedicated developer focused on tracking standards or making usability improvements, instead of training multiple generations of users that XML was slow and hostile to users. Various XML committees’ travel expenses building standards which were never used likely cost more than that. Not leaving XPath frozen around the turn of the century would have helped in so many places.

The other wart I think would have made a surprising difference is the usability disaster around namespaces. So many tool developers forced users to switch between the short namespace:attribute form they used everywhere in the document and the {namespace url}attribute form that resolves to, or forced you to respecify the namespaces on every operation rather than reusing the values the parser had already loaded. Users begrudged that verbosity but they hated it when it meant something silently returned incorrect results because a selector using the document’s own syntax didn’t find the element they could see using those exact values. Absolutely nothing anyone did in the XML world was a better use of time than fixing that would have been since it trained people to think of XML-based tools as a painful, error-prone experience to be avoided — and they did as soon as they could.
That's pretty much the stated objective, in addition to designing the protocol in a way that freezes features at the outset to prevent it from becoming another Web 2.0.
How close did Skinner ever get to the concept of heavenbanning?

(an anecdote I've heard but can't vouch for: a consulting firm had been hired to redo elevator firmware, due to complaints of slow elevators in a skyscraper. The out-of-the-box cheap'n'cheerful solution was instead to put mirrors in front of the elevators ... and the complaint rate did indeed decrease)
Yes, it's expandable later. But in your initial implementation you'll still need to decide on a set of possible values, yes?
I recently searched for passport ranking and there are several and they do - of course - not agree. The first three search results for me are [1][2][3] but there are certainly more and the different results are due to the metric used - for example, is visa-free as good as 90 days visa-free and if not, how are they weighted?

[1] https://www.passportindex.org/byRank.php

[2] https://www.henleyglobal.com/passport-index/ranking

[3] https://www.globalcitizensolutions.com/passport-index/global...
I'm a fan of Lynx. React and angular have destroyed the semantic web.
It doesn't matter for you personally, but it kind of matters globally. If everyone hits that same inefficiency at the same time then there needs to be a lot of extra capacity in the electric grid that can be spun up during a small part of the year.
I'm sure that's based on your long experience setting up mining operations?
Nice, thanks for the reply. Our Python tests run incredibly slowly. Having fast tests makes such a big difference. It can be really demoralizing waiting for a bunch of tests to finish. In general, I'm incredibly excited for how fast Go is, especially compared to Python. I had almost forgotten what fast feels like.
Strong competent management does solve this, but it’s oh so rare.
There's an "Improve My Travel Freedom" tab
I would prefer if logically nested blocks could also be phyisically nested (and indented), so you can have a full tree structure. If you're describing something that can have variable levels of nesting (think folders) then it can sometimes make the format easier to understand.
Drugs, robots and pursuit of pleasure – experts worry about AIs becoming addicts
It can be useful to distinguish between domain objects and objects that you use at the edge of your service, like on the API. They might have different annotations or you might want to evolve them differently, e.g. your domain objects might change while you want to keep your API the same so as not to break your consumers. Things like that.
> Merkel on "tricking Russia into a ceasefire"

Once again this is a complete fabrication. Here's Google translate of the linked section:

But that presupposes also saying what exactly the alternatives were at the time. I thought the initiation of NATO accession for Ukraine and Georgia discussed in 2008 to be wrong. The countries neither had the necessary prerequisites for this, nor had the consequences of such a decision been fully considered, both with regard to Russia's actions against Georgia and Ukraine and to NATO and its rules of assistance. And the 2014 Minsk agreement was an attempt to give Ukraine time.

There is nothing there that even comes close to the claimed quote (and quote marks imply an actual quote).
S-expressions do not necessarily imply Lisp nor an executable environment, it's a (family of) syntax(es) to build a document format. Like EDN.
The issue I’ve seen is need for heat goes up a LOT in older houses when it gets that cold, and the heat pump without resistive heat performs a lot worse (like 2x+ worse).

So it’s a noticeable combination
Sure, I can't imagine it being too difficult to compromise the keys for some first world country.

But there's no need to bother, you won't get busted at an airport because the chip of your passport failed. If they were suspicious, they'd just go through a document verification checklist and see if your passport has the correct physical features. Check out the PRADO glossary for example https://www.consilium.europa.eu/prado/en/prado-glossary/prad...

A bunch of EU countries still issue non-biometric passports, even if with limited validity periods.
My wish for a dream config language is this: Allow a choice between unambiguously-typed expressions (quoted strings, only true/false, decimal numbers) and explicit type annotations. So this:

regions: $[string]
- no
- se
options: ${bool}
a: yes
b: no

(with possibly a different syntax) would be equivalent to

regions:
- "no"
- "se"
options:
a: true
b: false
But it does mean you need a reliable backup heating system, because the very inefficient at -20 is also when you need the most heat.
Typically these systems underperform because they are tested in ideal lab conditions, but then the actual installation has lots of non-idealities (long pipes with lots of bends, dirt, dumb thermostats, wrong flow rates, poor airflow, blocked filters, things cycling on and off, etc).

The full report that the (uncited!) diagram is from is here:
https://acep.uaf.edu/media/290488/Air_Source_Heat_Pump_Poten...

The report describes a few other heat pump models which do meet the advertised specs.
The reason why China dominates supply is their willingness to operate the incredibly dirty refining process.
The current politics around this issue is not simply about free movement. It is about economics. For example, it is easy to travel to Denmark, using Denmark as an example of an "enlightened" state. However, if you intend to stay for more than 3 months, you must secure work/residency before even arriving. State benefits are also available only to citizens and others of certain legal status, with more limited benefits available to EU citizens.

The actual question that is being debated is allowing free movement into this country while at the same time providing full benefits (welfare, housing, health, etc) without requiring job/work permit/etc.
The whole "code is a liability" mantra needs challenging IMO - it's too simplistic and "cargo culty". It's a misappropriation of a financial accounting term (where Assets = Liabilities + Equity) and liability also carries with it all kinds of negative associations.

It has a value in making businesses aware that production code has an operational cost just to keep it "alive". And it's useful for tempering junior developers who haven't yet absorbed principles like KISS and YAGNI.

But it fails to factor in the relation between code and an organisations ability to make (or save) money from that code. For example the capabilities of your code may be a competitive edge for your business. 10 lines of code which uses CPU and memory inefficiently may end up being more expensive than 1000 lines of code which uses CPU and memory _efficiently_ and leads to lower infrastructure costs as usage grows.

As far as I'm aware the term goes back to 2007 - https://web.archive.org/web/20070420113817/http://blog.objec... - a time where businesses hadn't really understood how to manage software based businesses, so it was a useful concept to help management become more mature about how they think about software.

But these days knowledge of how to run software based businesses is far more widespread - we don't need to simplify our thinking to "code is a liability".
As an aside, I really cannot for the life of me imagine paying $15/mo for TechCrunch articles like this.
Its clear to everyone banning gas ranges isn't the plan. The CPSC is lying to encourage people to buy new appliances. As opposed to cutting a hole in the wall for ventilation. For the benefit of climate.

Editorialized title: Lying for a Climate Crusade
I think it makes sense. Of all those combinations, only Trump attempted an insurrection. So if this is a bias, it's not a bias against conservatists, it's a bias against trying to overturn legitimate election results.
> will this algorithm uncover a new design space for NNs?

No.

Hinton "discovered" stacking ensembles and gave it a new name, fancy analogies to biological brains and then made it worse.

The gist of this is that you can select a computational unit, be it a linear layer, or a collection of layers, compute the derivative of the output with respect to the parameters, and update them.

Each computational unit is independent, meaning that you don't calculate gradients going outside of it.

This is the same as training a bunch of networks, computing predictions, and then using another layer to combine the predictions. This is called stacking, and the networks are called an "ensemble". You can do this multiple times and have N levels of meta estimators.

Instead of fitting the ensemble and then the meta estimator, Hinton proposes training both simultaneously but without allowing gradients to flow through.

That is stupid because if you don't allow gradients to flow through, you will see a context drift as the data distribution changes. Hinton observed this context drift, to deal with that, he proposed normalizing the data.

On one extreme, you can use individual linear units as the models, and on the other extreme, you can combine all units into a single neural network and treat that as a module.

So no, this does not open any new design, it's an old idea, worsened, and wrapped in fancy words and post-facto reasoning.

If you are curious how a linear layer is an ensemble, observe that each vector is its own linear estimator, making the linear mapping an ensemble of estimators.
Salary adjusted after not moving to the city
Val[0] language?

[0] https://www.val-lang.dev
What is the different between this and mastdoon website?
This morning it shows the total loss (or gain) for all time in every view.
Only for mac

Why not put this in the title
And to me the crux of the matter is whether the systems are safer despite any phantom braking.

The focus on perfection rather than improvement is surprising to see on HN.
Aerodynamic drag is cD multiplied by cross section. By virtue of about a quarter the cross section of an average passenger vehicle, motorcycles are far more efficient. Don't even get me started on road wear being a function of weight to the fourth power, thus motorcycles effectively cause negligible road wear.

For what it's worth, I've never driven a motorcycle and probably never will, for danger.
Thanks for the pointer. I’ll look into Chiltrix. However, based on my state’s tracking of heating fuel prices, wood pellet is by far the cheapest [1] and is a local/regional resource.

[1] https://www.energy.nh.gov/energy-information/nh-fuel-prices
While on the topic of FFT, the "butterfly diagram" sure is profound, although it takes me effort to wrap my head around it to make it a personal favorite in the same way that other illustrations make things click to me.
My analysis is not limited to the “most talked-about layoffs” (whatever that means) nor is it limited to some cherry-picked old cash-cow behemoths that are going to have much slower growth rates going forward. Possible exception is Facebook if they can make the VR bet work, but I have serious doubts about VR being commercially profitable within the next 20 years and even more doubts Facebook will be the company to make this happen.
Off topic, but people need to stop saying that it's an "$X billion startup" as if it's a real thing.

It's not. It's just a private valuation on a piece of paper, not real money you can readily exchange for real cash.
"quietly" except they're loud about it
The only heating around here these days is electrical (edit: except for wood stoves, which are usually allowed). Oil isn't allowed, and gas heating doesn't exist. So yes, "no gain" means that the heat output is equivalent to the electricity input (at the low turning point, which is around -20C for my pump - I should qualify that though, it used to be when it was new, but the tech who checked my pump a couple of years ago said it had lost some of its efficiency due to various things including some difficult to remove grime inside, but there still was no point in actually replacing it).

Of course, there's also the installation costs of a heat pump. But it did pay for itself in a reasonably short time. If it hadn't been that efficient it wouldn't have - first, there's the actual price, which is not as much these days as it used to be, but then there's the actual installation by a pro, and I believe that part has only gone up since then.
The other issue is that a heat pump has to keep the output temperature relatively low to stay efficient - so just dropping a heat pump in to replace a wet heating system with a gas boiler will have two problems - the total power is less, and the amount of power the existing radiators can deliver to the room is too low. Effectively heating a house with lower temperature water needs big radiators or wet underfloor heating.
westworld beyond season 2 was a dumpster fire anyways. an obvious example of poor long term plans.
We have such a thing (some Mitsubishi model I will check later on if needed\) at home in Catalonia. Works OK, but the house despite being well isolated in general has a weak spot: dark external blinds. Without some external shading these warm up in no time, so the air between blinds and windows goes probably +45C or more.
To combat this the heat pump in the air condition mode has to work way harder.

So a bit like with a Victorian house in winter where isolation is the key: one has to start with making sure that the house interior gets as little heat from sun in the summer as possible.
This index needs to be adjusted for desirability (does anyone want to go there?) and economic ranking (% of world gdp accessible)

Visa free travel to Vanuatu, South Sudan, and North Korea != New Zealand, Botswana, and South Korea
In MySQL the `utf8` character set is originally an alias for `utf8mb3`. The alias is deprecated as of 8.0 and will eventually be switched to mean `utf8mb4` instead. The `utf8mb3` charset means it's UTF8 encoded data, but only supports up to 3 bytes per character, instead of the full 4 bytes needed.

https://en.wikipedia.org/wiki/UTF-8#MySQL_utf8mb3
read some books about how to deal with people on the spectrum - which is what you're really asking about.

Usual acronyms of Asbergers, ADHD, ADD, PDA etc. "difficult engineers" is not something that exits in this world.
There are difficult people, sometimes highly ordered jobs (like programming) attract people who like order -> many of which are on "the spectrum".

Be human, Be Kind and understand how to communicate effectively with several types of people.
Mapperly – A .NET source generator for object to object mappings
Rishi Sunak facing major Tory rebellion over internet safety law
Being unpractical is the point. It's unpractical to implement tracking, anything beyond simple ads, websites with flashy or distracting designs, picture-in-picture video autoplay like news websites often do, popups, moving banners, and RAM/CPU heavy client-side scripting (or any client-side scripting, for that matter). So your website will have to do without that.

And that is by design. Gemini is designed to exclude those features, because the target audience of this protocol wants to browse a web where those features are impossible to include.
Yeah, in Russia the society is quite racist towards the Caucasus Caucasians. How's that for affirmative action? /s