skysight-inc/HackerNews huggingface dataset:
You make a good point. But that's something I'd iron out before co-founding together. Co-founding is like getting married. Essentially you're saying "yeah, she looks like an alien dissected a train wreck and put it back together inside out, but she's really smart."

Some people are okay with that. Some aren't. Are you?

And what good are experiences and interests if your visions aren't in line with each other, or you end up just never liking the guy? I mean, if you can find things to like and get along- that's great! But the fact that you're asking this question to begin with is troubling in itself. You shouldn't have to ask, IMHO. You should just know. And, I suspect you already do.
I want to manage passkeys myself. I don't want to use iCloud Keychain sync, and I don't want to use 1Password. This is a non-negotiable requirement for me. Other than that, I'm fine with the idea.
Or maybe he recognizes that it’s literally impossible to train a system to output a result that isn’t biased. Creating a model will result in bias, even if that model is a calculator. You put your perspective in its creation, its utility, its fundamental language(s) (including design language), its method of interaction, its existence and place in the world. If you train a model on the web, it’ll be billions of biases included, including the choice to train on the web. If you train on a “sanctioned list,” what you include or don’t include will also be bias. Even training on just Nature papers would give you a gigantic amount of bias.

This is what I really don’t like about the AI ethics critics (of the woke variety): it’s super easy to be dismissive, but it’s crazy hard to do anything that moves the world. If you move the world, some people will naturally be happy and others angry. Even creating a super “balanced” dataset will piss off those who want an imbalanced world!

No opinion is “correct” - they’re just opinions, including mine right now!
I have kholed at a clinic multiple times . It has been a profound experience
So tell me, who is making microservices for calls that could be done wholly in memory? How are you handling rollbacks and such for this in memory logic?

Aren't you still writing out to external data stores? If that's the case then its really not a comparison of in process to a RPC, it just two RPC hops now, no?
As a data point, I run an open SSID with QoS limiting throughput to 1.5 Mbps that permits only ports 80 and 443. It's enough for someone to check their email (or homework).
If you have a tagged union type with Boolean literals as the tags, like in the slack api, then you can’t say ‘if not res.ok’ to narrow the type, you have to say ‘if res.ok == True’

Which isn’t very pythonic imho

Also I’m pretty sure ‘if res.ok is True’ doesn’t work
Thanks for offering, more looking for a dumbed down version of this paper. I can't understand what the figures in the article represent our communicate.
And even then, SafeHandle is a much better option.

Memory deallocation can be done as deterministic as malloc/free via the native heap APIs.
This is awesome! A nice replacement for the Duckling service if you need fast regex based NER in your code.
Any1 built their own battery-arrays? I am interested in solar in part to avoid blackouts. But for that I will need batteries. And my house being 100% electric, tesla's powerwall quickly becomes expensive. On a first glance, using lead-acid batteries appears to be straightforward, but I wonder what edge-cases and gotchas others experienced with it. How much time is needed to maintain it.

So far 10kW gas generator was able to power most of the house's essentials before resistive heater kicks in in HVAC system (two heatpump units, each has a 7.5kw resistive heater as a backup when outside temperature drops too much.) But I would feel better if I did not have to rely on availability of propane/gas and clean roads during periods like 2021 blizzard in Texas.
Unfortunate, an opportunity to further enlighten others, but the author took a dismissive and antagonistic perspective.
Umm, no.

The government forced the banks to take money so people couldn’t tell which ones were in real trouble and which ones were fine.
Wow nice! Thanks!
Currency counting is all done by machine. Sure I guess a teller has to load the machine and push the button, but it takes seconds to count huge numbers of bills.
Yes it is, there's a connection fee of approximately $10/month for that same reason. Net metering is a totally unrelated topic. What's being argued about is the rate. Until now, rooftop solar customers get a retail-level payback for excess production sent to the grid. Under the proposal, this payback would be at the wholesale price, which is significantly lower.
Show HN: Y2K – A 0-byte code golfing language using pre-2000 timestamps
Happy New Year HN. I thought it would be a fitting time to share a project I've been working on called Y2K. It's a code golfing language that can interpret file timestamps as code and ignore all file content, effectively allowing a set of 0-byte files to collectively form a solution to a problem. The repo has some small examples, including a simple "Hello World" program, printing the Fibonacci Sequence up to N terms, and Fizz Buzz. Most of the current examples only create 1-3 files when exported.

To make it easier to write programs, the interpreter allows writing all logic "raw" as file content, rather than requiring users to manually modify file timestamps one by one. These files can then be exported to a set of 0-byte files with their timestamps modified to achieve the same functionality.

It's still in a fairly early stage and has quite a few limitations, but I'm curious what people think at this point. It's been a fun project to work on and I'm excited to continue expanding on its functionality moving forward!
There is also, particularly post 2008, an exaggerated sense of criminality in our financial system that made people who otherwise would have moral qualms about what they’re doing embrace or even work in crypto/web3 because, in their minds, everyone else is scamming anyway.
KDE Highlights from 2022
Because they order twitter to hide accounts they don't like in India.
>doing the conversion between bytes and string implicitly

There was no conversion. `bytes` and `str` were the same type.

http://docs.python.org/whatsnew/2.6.html#pep-3112-byte-liter... says:

> Python 2.6 adds bytes as a synonym for the str type, and it also supports the b'' notation.

I just checked in Python 2.7:

>>> bytes is str
True
>>> print("Hänsel")
Hänsel
>>> "Hänsel"
'H\xc3\xa4nsel'

I'm working with Germans, Japanese and Polish that use a lot of special characters, including Kanji, umlauts, extra quote characters etc. I need the non-ASCII parts and had no problem with them in Python 2 on Linux (now, C++ libraries that reinvented their own string classes: many problems; C libraries: no problems).

The point is when bytes is str, everything works just fine in Python 2 Linux with UTF-8 locale (which are used in all modern Linux distributions). No need to have a distinction between bytes and str.

That how the rest of the OS works, too. Even a lot of Gtk, Glib and so on (for example the GNOME desktop environment) assume that you are in an UTF-8 locale for file names, for example.

> A more abstract "string" type is all they need, without worrying about how it works under the hood (and if they do, they need to understand how encode/decode works properly anyway).

Ehh, we had students write drivers for measurement apparatuses and they all used Python 2 str (without being prompted to do so). No encode or decode anywhere. Of the students, almost no one who tried Python 3 for that stayed with it (instead they were using Python 2). There was just no upside for this use case.

I agree that, long term, having a distinction str vs bytes makes sense. But then you ARE juggling things that the OS doesn't need--it's basically busywork in Linux.

I'm not trying to minimize your experience--but I don't think it would happen if you tried python2 on Linux today. Not sure it was worth it breaking compat for that.
For free customers, that's okay I guess, but not for paying ones.
That's right. But I find that meeting organizers are reluctant to cancel instances of a meeting even when they don't have much to share, because they are unsure in advance if others on the meeting may have something to bring up.
> If customer service were a priority companies could figure out how to build a trustworthy workforce.

This is 100% accurate, in my experience. You even gave the answer in your first sentence:

> these are low-paid jobs with no agency.

If they weren't low-paid jobs with no agency, a lot of trust and retention would follow, almost like magic. (Of course there would still be people who abuse or mess up the intended system; that's why you have internal business controls and vetting.)

A long time ago, I worked overnight customer support for a very large ISP, via an outsourcing company. On the overnight shift, there was no distinction between technical support and billing because call volumes were so much lower. Also because of being on the overnight shift, we had much greater authority to make account adjustments and fixes because the employees who worked directly for the ISP didn't want to be woken up in the middle of the night to approve requests. All we needed was a second coworker to sign off. Oh, and we got paid a 25% differential for the shift.

People would actively try to move onto the overnight shift. Our group inside the outsourcing company had the lowest turnover rate by far and was helped by one year our overnight shift had zero turnover. Two of my coworkers even declined being promoted to daytime lead so they could stay working overnights.

Yes, the pay was good even though the hours were not so great, but the autonomy was better. We were treated like adults; we didn't even have a technical support script because no one from the ISP had come to officially train us so we weren't "allowed" to use the script in the knowledge repository. We had access to the billing tools that would tell us why an account was in a certain state and so we could actually fix, or at least tell the customer about, problems instead of offering them a "trouble ticket" and a "one-time credit of $15 for your issue."

It was amazing and I'm often sad that our industry has forgotten that humans are the point of all of this.
https://github.com/microsoft/Recognizers-Text/blob/master/Pa...
The original comment is as nice as it needs to be.
Interesting. I have zero experience with Drupal, but I assume its similar to WP in its architecture since you bring it up :)

I think any good solution to working with these 50/50 code and configuration mgmt technologies have to start with a solid analysis and understanding of what the actual business needs are(?). And then (re)evaluate how things are done.

And then perhaps also pricing models when it comes to the ‘“managed”’ part you mention. I think, for what Im building, there will end up needing to be a “managed hosting” offering which is more restricted and a custom development/T&M work which will be hourly.

Could be interesting to compare notes when get more of the setup up and running
http://web.archive.org/web/20230103113223/https://www.nytime...

https://archive.ph/FdubE
Yes, but I think this is the ultimate fate of most successful languages. New languages start small and elegant, and everyone raves over them, then over time new features get added, and added ... and eventually the elegance and othogonality disappear. If this was a program rather than a language, now would be the time to refactor, but you can't because of backwards compatibility, so eventually you get to c++-like bloat. I actually like c++ -, but it's definitely out of control at this point.. although many people just ignore the bleeding edge features and basically code in something closer to c++11.

Languages really need to evolve to stay alive, but the evolution will eventually kill them!
Companies can keep profit margin flat by increasing operating expenses such as salary. For PG&E it looks immoral.

https://www.ewg.org/news-insights/news-release/2022/10/ratep...
Worth noting that dev.to (and hashnode.com that someone else mentioned) has such a bad reputation for low-effort low-quality posts that's shadowbanned on HN. And nothing of value was lost meme is very applicable.
Overall an interesting post, thanks for sharing.

Nitpick for OP (@palant): on mobile Safari (haven't checked any desktop browsers), the images embedded into the post appear stretched out vertically (i.e., too "slim"). It is still technically readable, but very noticeable and jarring. This only applies to the images when embedded, opening direct image URLs in a dedicated browser tab renders them properly without any stretching. I suggest checking CSS, but that's just my first guess and could be entirely wrong.

I think just keeping the same horizontal size of images, but reducing the vertical size, would make it much more aesthetically pleasing + readable.
Almost everywhere this discussion takes place, for years now, seem to agree zoning is the cause and solution. But I've yet to see a single city or county do anything about it. Just repeating this line will not do anything, and clearly voting wasn't able to solve it. So what will happen?
My understanding from following a few economists on this topic is that rent is a major factor. Here's a Vox article talking about the correlation between rent and homelessness

https://www.vox.com/the-goods/2018/12/14/18131047/homelessne...
Additionally, the worst strains on the grid are really measured by the peak loads, so if you change billing a way that makes the peak energy less expensive, and therefore disincentivize people to (a) reduce usage at peak times or (b) install solar panels/batteries to mitigate their peak usage, then it actually might make the grid more unreliable.

Water is different in that we really only have usage concerns about water, AFAIK there is never any issue with the water pressure drops at peak times (perhaps thanks to water towers). With electricity the concerns are mostly about the peak usage, and not so much the overall usage.
What the parent is saying is that "Real X has never been tried" is a common dodge for people defending the indefensible, because it's unfalsifiable. It also fails to take into account human preferences that are preventing Real X. FTX wasn't centralized because they were mustache-twirling villains who hade decentralization, they were centralized because that's what the market demanded, because DeFi is impossible to fucking use so nobody does.
The first Twitch outage of 2023 takes down everyone’s stream pages
Articles with titles like "How I spent 3 weeks discovering that Nagle's Algorithm exists" are a HN staple. Turning off Nagle follows the principle of least surprise. This article is the first time anyone has ever written about being surprised by Nagle's Algorithm being off.
I wonder if it's time to prioritize newer books with mysterious titles such as "Transfer Learning for Natural Language Processing" over traditional SE books. I imagine this year we'll see some "Programming in chatGPT" ones too. Are we experiencing a revolution in code generation or is it mostly hype still?
> we'd just get tons of utility scale solar installs

This is happening, in a big way: https://emp.lbl.gov/utility-scale-solar/

The main limitation AIUI is grid interconnections, i.e. there are a lot of projects in the backlog that can't be built until the utility approves and prepares for it.

https://emp.lbl.gov/queues

> The lists of projects in this process are known as “interconnection queues”. The amount of new electric capacity in these queues is growing dramatically, with over 1,400 gigawatts (GW) of total generation and storage capacity now seeking connection to the grid (over 90% of which is for zero-carbon resources like solar, wind, and battery storage).
> but when it comes to crypto sophisticated quants and Joe Bogsly are operating on a level playing field

Pretty sure Tether isn’t operating on a level field with Joe Schmoe.
Note: I am the author of this article.

Where did you get the idea that direct network access is required? To quote the article: “large applications interacting with websites in complicated ways.”

Most attacks can be launched by an arbitrary website. And given the number of people affected, this is way worse than any individual server being vulnerable. Besides, I’m definitely not going to look for server-side vulnerabilities without permission.
Thanks. I think the supply chain may be too long and filled with unwarrantable code to be able to actually have real warranties.
A few years ago a YouTube video about the movfuscator set me wondering about just how minimalist an instruction set could be without hurting code density (unsurprisingly programming with just MOVs yields spectacularly bad code density!) - and ultimately led to me embarking on my own toy CPU project!
I had a fucking blog on Tumblr but then they banned pornography.
I think it's fair that you would appreciate a warning.

In the blog post your claim that "small businesses cannot depend on huge providers like google or cloudflare" may or may not be right, but it's absolutely not evidenced by you not reading the TOS.

I suppose you're also right that there's no way to monitor whether you would be considered an image proxy. I would appreciate more clarity on that myself.

It's extremely clear in your case though. You said it yourself, "all my subdomains that operate as image proxies are banned."
How do microservices help here? You can deploy a monolith 10 times and have the same risk distribution.
Finland and Estonia weren't planning for a new terminal but in February of course realized they needed one. The countries are connected by a new gas pipeline so share a common interest. They started a race to construct the ground facilities and acquire a floating terminal ship. Finland was farther along in the construction and it was decided to place the terminal there. It started supplying gas to the grid in in December. It's not famous German red tape so I guess doesn't make the news.
https://lngprime.com/europe/finlands-first-fsru-begins-suppl...

Nowadays almost the whole of Europe is connected by international gas pipelines. Of course there are flow constraints, but it's hard to completely cut off any place. In theory one could send gas from Norway south through UK, Holland, Germany and Poland and then back up north through Lithuania, Latvia, Estonia all the way to Finland.
Add the terminals dotting the map and it's a pretty resilient system. This is a nice resource. https://www.gie.eu/publications/maps/gie-lng-map/
We're the "majority" by virtue of internationally gerrymandered borders. In the region as a whole? Yes, we're an indigenous minority.
Note that merely having solar panels on your house doesn't automatically let you run your house off of the panels in the event that the grid goes down. Firstly, if you're connected to the grid, then a single house trying to push power into a downed grid would be like trying to refill the ocean with a super soaker. Even with lots of houses doing it, the frequency would be wildly unstable at best and cause damage to equipment. Secondly, it poses dangers for lineworkers who are probably trying to resolve the outage, by putting surprise voltage into wires.

It's certainly possible to have a solar installation that does let you disconnect from the grid, but it requires extra hardware (including a battery backup).
> Somewhat surprisngly, indentation-sensitivity in languages like Python and Haskell had me writing cleaner-looking and more readable code by default.

Yeah, I've gone from hating this, to accepting it (after using Python), to wanting it if I were to design a language (after using Haskell/Purescript/Idris).

> Based on this experience alone, if I were to design a non-S-Expression-based language, it would push me toward indentation-sensitivity.

The catch is that it's a pain to parse. Haskell and Python do token injection. Idris has some manual checks (with lots of holes/exceptions) and explicitly passes around an indentation (in some places). A few others conflate parsing and lexing.

I've settled on having a `(layoutRow, layoutCol)` in the state and requiring `col > layoutCol || row == layoutRow && col == layoutCol`. This lets you setup the off-sides layout and still accept the first token at that column.
Selectively reporting a common behaviour is indeed propaganda.

You are trolling by casting the allegation as “confusion”.
Schneir on Security wrote about this paper [1], and there’s a HN discussion about their post [2]

[1] https://www.schneier.com/blog/archives/2023/01/breaking-rsa-...

[2] https://news.ycombinator.com/item?id=34235350
In the Netherlands you a fixed price for being connected. The amount varies on the size of the connection. Usually 1 phase 40A is as expensive as 3 phase 25A. Anything above that easily triples in price. Aside from this you have net metering still and you pay for what you consume. No “usage bundle” is included in the connection fee.

Also, the companies for infrastructure and that provide the actual energy are separate but the energy supplier charges for the infrastructure provider. The infrastructure provider is semi privatised while the energy supplier is fully privatised.

It kind of works, except that we need like everyone else, to upgrade the power grids to deal with increased consumption and we haven’t invested in that.
You're welcome!

Plus ça change, plus c'est la même chose
I too made a bunch of money on BTC but in the end, it was just gambling. Got lucky, nothing more, nothing less. I did not know anything, the future just landed on what I thought would happen. Survivorship bias at it's finest.
Another way to look at this is microservices reduce the blast radius of problems.
Eventually, developed and aging countries like Japan or South Korea have to import immigrants or simply die away gradually. Either way, their cultures are going to cease the way they are today.
3.25% of fifty bazillion ain't so bad.
Yeah, it's bin packing, not straight efficiency. Also, people seem to exaggerate latency for RPC calls. I often get the feeling that people who make these latency criticisms have been burned by some nominal "microservices" architecture in which an API call is made in a hot loop or something.

Network latency is real, and some systems really do run on a tight latency budget, but most sane architectures will just do a couple of calls to a database (same performance as monolith) and maybe a transitive service call or something.
This study, and the person you're replying to, are using the term disagreeable in the Big Five psychology sense. They don't mean unpleasant, cynical, or snarky. Sometimes disagreeable people are snarky, but they don't have to be.

You do, actually, have to be disagreeable to disagree. Agreeable people don't like to cause a fuss and just go along with stuff even if they disagree internally. Disagreeable people are the people who tend to disagree. That's all it means. Some of them are snarky assholes (you right now?), and others are just people who disagree.

"Disagreeable" in common parlance means difficult, overly-critical, and aggressive, but that's not what 's being said here.
Aah, yes. The old fine print switcheroo.

"Here's a tool for this highly specific purpose!†"

"†Tool not fit for this highly specific purpose."
> otherwise we could switch to electric heat but that is a huge outlay.

You can walk into any major retailer, buy a space heater, and plug it into any outlet in your home. Keep in mind that your gas furnace is turned on/off using a thermostat and temperature setting, so if you reduce the set-point e.g. 1 degree, and then either locate the coldest parts of your home or areas you want to prioritize (e.g. livingrooms/bedrooms), you can then target space heaters into that location to offset the savings from gas.

In terms of deployment heating or cooling, electric heat is the cheapest and easiest. You're just thinking that it must be whole-home or nothing, which isn't the case, you can reduce your whole-home and spot-heat as needed.