skysight-inc/HackerNews huggingface dataset:
My attempt from many years ago in GWAAAAAAAH. A brainfuck like programming language, for crazy rabbits where most characters are ignored and only for style.

DAAAAAAAAAAhhhhhh ?

Rooooaaahahhahah!!

GAAAAAAAGAAAAAAAAAAGAAAGAWWWWOM!

GAAH!!
GAH
AAAAAAAH!

Haaaaaooa

BrrooaAAAH
GAAH

WWAAAAAAAAAAAAAAAH!!!!!!!

GeeaaahH!
AAAH

OOOOOOH

BlOOOOOOOOpppH

GAH!
GobidoaaahH !
If you see somebody behaving like that, report them to GitHub so they don't do it to anybody else. The link is on their user profile page.
Check out LD_PRELOAD on Linux, it is the same concept.
I looked into the IR blasters before, was wondering if they're strong enough to transmit to multiple targets.

I've previously written a Telegram bot, so was thinking to reuse some of that.
This is pretty much caveman/child logic though. You can make anything sound anything speaking like that ignoring all the complexities involved and actual value provided.
I agree with readme needs to specifically mention unimplemented features. But the responsibility for using an unpopular library lies fully on the user, not author. Of course if the library is popular, author needs to maintain it, or delegate auhority to other maintainers.

As user, it's clear that you need a feature which you found on an unpopular library. Now rather than be skeptical and research the library, or wrap it under yours so you can replace it later, or develop your own, you decide to blindly use it and blame the author.
In the way that, as an engineer not working directly on Kafka, the only thing I ever hear is when data it's missing because Kafka is broken. That might be down to my company not using it correclty, or it being a finnicky tool, but it doesn't look good.
This is one of the best interviews I have ever seen. The interviewer is really good and some of the stories are amazing.
I assume there's a level of connection that is differently deeper with people nearby. Unless you really have good solid feelings for the people you talk to online, but I never feel the same when I meet someone I like to be in the same room with. It's less fickle it seems (<= emphasis on seems). There's a lot about internet that was about freeing yourself from geography. No more locked in your local culture. I believed it was necessary but I think otherwise today. I value local a little bit over my personal clicking with people on the other side of the planet.

My 2 cents
HrefHunt is awesome! Thank you. Crawling through it for my spartan collection: https://old.reddit.com/r/SpartanWeb/
This is neat. I’d love to be able to code in an iPad.

Related, I found GitPod a while back, it offers a VSCode experience and also manages running services for you.

https://www.gitpod.io/
May be he meant bowl.
Nice concept and cool animation!
Was that the inspiration for this? https://isotropic.org/papers/chicken.pdf
NASA – Cave of the Winds [pdf]
Time stamp + TZ is a useful feature if you want to store TZ along with the time stamp. But I think that’s nearly always a bad approach. The only part of your system that needs the time stamp converted into a TZ is your human user. Performing that conversion on the presentation layer will almost always lead to less complexity.
Chicken, Chicken Chicken [pdf]
I think a lot of this type of writing shifted to Twitter and Instagram, but I agree this microblogging is not the same... it lacks the immersiveness of a good long story.

On the other hand it has never been easier to set up your own blog with services like Netlify, Jekyll, Pelican etc.

I recently started my own blog in this way, however it requires some coding skills... I know it’s a shameless plug, but here it is: https://haltakov.net/blog

To not be too selfish, let me also share one of my favorite blogs of a guy telling amazing stories about his hikes and adventures (unfortunately, he hasn’t written in a while): https://www.otherhand.org
> There aren't any "magic scheduler hints", either. You can assign a scheduler to each virtual thread, and that scheduler makes the relevant decisions. That's the same separation of concerns that native threads have, too.

I'm thinking of when you need to "pin" to a particular native thread. In a native-threads + async/await language you have direct and visible control over where that happens. In a green-threads language it's going to involve magic.

> Having said that, I don't claim async/await isn't a good solution for some platforms, and in some cases there's little choice. For example, Kotlin has no control of the JDK, which is necessary for lightweight threads, and languages with pointers into the stack as well as no GC and lots of FFI might find that a user-mode thread implementation is too costly. But I think that in cases where usermode threads can be implemented efficiently and in a way thar interacts well with the vast majority of code, they are clearly the preferable choice.

A priori I agree. I expected green threads in Rust to work out too. I just can't get past having seen it fail to work out so many times. Maybe this time is different.
I wish the paranoid dreams of conservatives were true. Google SHOULD censor conservative propaganda like Fox.
For my own managed funds/indexes, I use https://m1finance.com, also with no fees.

You specify pies of funds with weights.

They automatically allocate funds and dividends to the underweight entries, and have 1 click for rebalancing.

It's not made for single-real time trading, there's one trading window each day.

Sure beats the spreadsheet and whole-share issues when I did it for free with Robinhood.
> The primary consideration at this point is cost.

Certainly. In my experience the operational cost of kafka is enormous. Ive seen incidents too often for a relatively small (<10 machines) cluster. I would expect that after a first long phase of finding the right configuration, to step on a phase were it runs smoothly, but I didnt see it yet.
I don't understand people who have serious hereditary medical conditions and have children. Yes, I know that "I just don't get it". Though I do have friends for whom serious illness in the family is the reason they don't have biological children.

I do find it a bit selfish to reject adopting a child (and thus presumably making that child's life better), instead of essentially saying "no, I only care about my own genes. If it's not from my body it's worthless".

I said I know people who chose to not have biological children for this reason. I also know people whose life is full of pain and suffering because they chose to reproduce their illness. One wanted multiple children, but after the first came with the illness they now know that caring for just that one (who will never not need help) is their full time job, so they can't have more.

And this in a country that actually greatly supports you. And it's not about the money.
Not to sound callous... but you took out the loan on those terms. Are they unfair terms? Sure. Were you ignorant and naive to agree to them? Absolutely. But should you also take some responsibility for the situation you now find yourself in? Yes, you spent $40k.

It sounds like you had to fight to get SSDI, not sure what that means, but at this point if you're making $1300/m you could start to pay off a loan that you took out and have a responsibility towards.

Again I don't know you or your situation at all but it sounds like you don't wanna recognise that at least a little bit of the problem is you.
+1 For crystal. I always post this project, an OS written in it from scratch, as it is one of the most impressive things I’ve seen on HN

https://github.com/ffwff/lilith
https://physicstoday.scitation.org/journal/pto
uBlock Origin 1.27.0 with interface redesign is out
> You shouldn't be using a KDF that takes significantly longer when the password gets bigger.

Your KDF necessarily takes longer when the password gets longer as it's a hash function and thus O(n).

For typical password sizes (typically under 64 bytes), you're below the hash's blocksize so the effect is nil and you can treat it as a constant but it will start coming into play as the size of the key and thus the number of blocks to feed into the hash increases.
Nothing improves a joke more than explaining it, like the article did. :-)
I expect word will get around about the "coasting", making it worthless.
It's actually p/e in the negatives. Anyway people should stop using it as some kind of god metric. It is easy to justify cases where large or negative p/e makes sense.
Skin also contains oils etc that have a part in the correct and healthy functioning.
Microsoft warns Berlin data protection authority
Big Tech searches for a way back into healthcare
Long term the Tillable idea won't fly. I worked with farmers as a fertilizer company agronomist for twenty years. If I understand it correctly Tillable is trying to insert themselves in the middle, acquire the right to sublease large amounts of land and mark it up.

Say you own a farm and lease it out. The family you lease your land to might be a neighbor. In the winter they might plow your driveway gratis. They add fertilizer and lime as needed. I've known farmers to even add small amounts of drainage tile at the beginning of a lease.

Now consider I'm a super large farmer who has rented your land through Tillable. Farming is a super thin margin business. I live two counties over so I am not going to plow out your driveway or look after your farm for you. I will pay top dollar, I will in effect mine your land to make a profit.

I won't put on fertilizer if levels are high and skip the lime. I will make a nice profit for a few years and then when yields drop I will drop the lease. Over time the price of the lease will drop sharply. So in effect the landlord will gain a few bucks short term but lose big time over the long term.

On a small scale I've seen this happen. When the landlord offers it back to the original renter he will be shocked and angry when he either refuses or offers a pittance.

The landlord either has to invest his own money on lime and fertilizer building the farm back up or have a series of short time renters from outside the county who take a chance on the land.
> Many small-to-medium size towns across the U.S. that once were economically prosperous, but no more. And times were too good to notice.

Why is the previous organization of society and industry "artificial" instead of what we have now?

I would argue that the current "ship things around the world to save a fraction of a penny" instead of "manufacture locally" is the "artificial" situation.

Our complete inability to adjust manufacturing in a time of great need due to Covid suggests that perhaps our modern organization is actually the wrong organization of industry and society.
YouTube Channel “Decino” is nothing but deep dives into Doom's Logic
What was it replaced with?
Can’t wait till Barr and every other member of the administration is on death row.
Making Decisions for Software Architecture and Scaling
I suspect that AMD disabled the 10GbE for EPYC, only enabled for EPYC Embedded. I heard somewhere that AMD want to avoid IP fee for mostly unused feature.

https://www.amd.com/ja/products/cpu/amd-epyc-7302p
https://www.amd.com/en/products/embedded-epyc-3000-series
> For example Forex trading in the City of London moves $6.6 trillion of money around, every single day. A Tobin Tax of 0.1% on that would raise $2.5tn a year - which would almost instantly wipe out the UK's entire national debt.

Traders can just move money to other trading system, e.g. futures, or they can just stop trading and instantly gain $2.5T a year in saved taxes, which is equivalent of UK's entire national debt!

If you want to capture these $2.5T, you need to close borders and tax these traders physically, one by one, like Soviet Union, China, North Korea, etc.
yes it's very much about having to go with the flow: in the past I've used Ruby for a swathe of scripting and prototyping tasks, fell in love with it and assumed it'd always be the go-to tool of choice, but now working on locked-down Red Hat envs where Ruby is not installed but Python is, so purely for that reason was forced to transition to using Python instead. Over the years since I've come to appreciate Python's virtues more, but still agree with your sentiment.
Different people have wildly different ideas about what the point of open source is.
What (defaults) in ISO8601 do you consider wrong?
How could one log in whilst having JS disabled?
In UTC leap seconds are not ambiguous because seconds are not repeated

> The extra second is displayed on UTC clocks as 23:59:60.

Note how it's not 23:59:59 repeated, and thus fully unambiguous
I don't think this is a matter of hype cycle at all. There are two things that changed:

1. Threading got much faster and lightweight. This is what Java was initially trying to work around, until it didn't have to any more.

2. The problem moved to handling as many sockets concurrently as possible. Even lightweight system threads are too heavy for scaling linearly with the number of connections (too much context-switching overhead, too much space for stack, etc.)

Green-threading has become a good idea again because we now have a kernel API that is used to multiplex a lot (but not all) I/O systemcalls.

Today Go runtime uses epoll/kqueue to read from a big bunch of sockets, whenever something new happens to any of them. This takes one system thread only.

The API model of epoll/kqueue implies some way to handle concurrency in your user code: this can either be callbacks (or async/await syntactic sugar) or green threads and CSP (channels and so on.) This is why green threading is having a comeback.

(Sorry for implying you did not read the article!)
I'll quote Doreen from elsewhere in this thread:

> I didn't get a diagnosis until my kids were like 11 and 14, I think. I didn't have to think about that aspect, in part because my first child was the result of failed birth control.
This seems to be using some sort of homegrown python system (migen) for fpga development.

If you really want to learn fpga/asic development do yourself a favor and learn a real hardware description language such as verilog or vhdl. It is really not that hard. If you have some minimal knowledge in digital systems you will be up and running in a few hours.

And with a good teacher it will be really fun:

https://www.fpga4fun.com/
"Net value taxation" is called inflation. 20% inflation will make everyone rich in no time.
I think the fact that you only got programming blogs says quite a lot about us and this community (even me, who I'm not a programmer)
Why would your employer decide what you do on your spare time?
But "company wide linters" do carry over to other companies and projects. For Go its already set up, you dont have to think about it. Otherwise youll have a week (or more) discussion for every single quirk in the language and how one would format that and try to apply this to a group of people.

I'd call them more like working standards. Imagine having to discuss how to make a brick wall everytime you need to make one. Things like having a masonry cord (which can equal to a "gutter", line length restriction) and the mixture of the cement, are critical for execution in a team of more than 1 person, and not following standards will make a hacked up job.
I don't think it's good to rely on the licence to carry this sort of information. Even if I have a library that I intend to maintain as polished and continually updated code, I'm going to have a licence disclaiming a legally-enforcible warranty.

And I might have a library that over the years changes from being shitty to high quality (and back!). I wouldn't want to go changing the licence to follow its lifecycle.

I think it would be valuable to have some widely understood conventions of text you can put in the README to set appropriate expectations.
Have you put some disclaimer about your situation and said that this repo won't be maintained and feel free to fork? I think it'll be the best resolution for your situation.
> distinguish between things that aren't meaningfully distinguishable.

Are these semantically the same?

Runnable action1 = () -> System.out.println("foo");
Runnable action2 = () -> System.out.println("bar");
action1.run();
action2.run();

var action3 = runAsync(() -> System.out.println("foo"));
var action4 = runAsync(() -> System.out.println("bar"));
action3.join();
action4.join();

> You only need to submit if you want to do stuff in parallel and then join (also, there are no extra steps).

I'm not comparing parallel to sequential. My point was that we're already doing parallel programming:

CompletableFuture<Result> fx = CompletableFuture.supplyAsync(() -> result);
CompletableFuture<Result> fy = CompletableFuture.supplyAsync(() -> result);
Result x = fx.join();
Result y = fy.join();

Parent doesn't like the existing parallel model. New model looks like:

// > plus no need for thread pools anymore.
ThreadFactory tf = Thread.builder().virtual().factory();
ExecutorService e = Executors.newUnboundedExecutor(tf);

// > No more [...] Completable<Future>, promises et al.
Future<Result> fx = e.submit(() -> { ... return result; });
Future<Result> fy = e.submit(() -> { ... return result; });
Result x = fx.get();
Result y = fy.get();

If going from the first to the second is an improvement, I don't understand the excitement. Especially when other languages look like:

fx <- async (return 3)
fy <- async (return 3)
x <- wait fx
y <- wait fy
I don't think any of these are particularly convoluted; they're in straightforward procedural code with a line for each letter. Most programmers could adapt the code to produce another string without too much effort.

What I'd consider convoluted is something like the Goodstein sequence[1] which would grow to monstrous proportions using far more memory than could be stored even if every particle in the universe represented one bit and far more time than beyond when the last black hole has evaporated, yet collapsed down (eventually) to "Hello World". (I've no idea how to do this.)

[1] https://en.wikipedia.org/wiki/Goodstein%27s_theorem
Photo Gallery: Barack Obama
> In a green-threads language it's going to involve magic.

No magic, just a custom scheduler for that particular thread. For example:

Thread.builder().virtual(Executors.newFixedThreadPool(1)).factory();

would give you a factory for virtual threads that are all scheduled on top of one native thread (I didn't pick a specific one because I wanted to use something that's already in the JDK, but it's just as simple).

> I expected green threads in Rust to work out too. I just can't get past having seen it fail to work out so many times. Maybe this time is different.

Implementing usermode threads in Java and in Rust is very different as their constraints are very different. Here are some differences: Rust has pointers into the stack, Java doesn't; allocating memory (on stack growth) in Rust is costly and needs to be tracked, while in Java it's a pointer bump and tracked by the GC; Rust runs on top of LLVM, while Java controls the backend; Rust code relies on FFI far more than Java. So both the constraints and implementation challenges are too different between them to be comparable.

Not to mention that they have different design goals: Rust, like all low-level languages, has low abstraction (implementation details are expressed in signatures) because, like all low-level languages, it values control more than abstraction. Java is a high-level language with a high level of abstraction -- there is one method call abstraction, and the JIT chooses the implementation; there is one allocation abstraction, and the GC and JIT choose the implementation -- and it values abstraction over control. So whereas, regardless of constraints, Rust happily lives with two distinct thread-like constructs, in Java that would be a failure to meet our goals (assuming, of course, meeting them is possible).

There are many things that work well in high-level languages and not in low-level ones and vice versa, and that's fine because the languages are aimed at different problem domains and environments. Java should be compared to other high-level languages, like Erlang and Go, where userspace threads have been working very well, to the great satisfaction of users.

Having said that, I suggest you take a look at coroutines in Zig, a language that, I think, brings a truly fresh perspective to low-level programming, and might finally be what we low-level programmers have been waiting for so many years.
> You probably won't ever see an EU broker offer free trades.

Freetrade, Trading212, both registered in the UK. (And I don't think 'transition period' would make a difference, but they're both years older than that.)
Yes it’s started by one man like Go by Dennis and Python by Guido and many more, only time will tell.
I don't think you understand what quant finance is about. Almost all quant strategies don't rely on speed. In fact, HFT is usually considered a totally different space than investing (and therefore quant investing).
I have no opinion on Detroit or crime rates in general. Just want to disagree that combining per-capita numbers is in some way misleading. Makes perfect sense for me and that is how I read the parent's comment -- combined and per-capita. Meant to illustrate the degree of the problem compared to other cities.
I worked for a company that made the same mistake but with AWS Kinesis instead of Kafka.

So, much more costly mistake.
The oldest person in the world was born in 1903, before George Orwell, Frida Kahlo and Lyndon Johnson. It's genuinely hard to fathom.
There is a way to switch the behavior in either systems, although each comes with its own caveat: https://www.howtogeek.com/323390/how-to-fix-windows-and-linu...
Probably payment for order flow and earning interest on cash, like everyone else. Or maybe they don't make any money, I dunno.
One earthly concern is that, because of this unified interface myth, management will think that once you integrated with one broker, the others come free because FIX.

Oh, you need another week or two with the other broker? Why? We spent so much just to get the industry standard API.

Sorry I'm too jaded to appreciate sequence numbering and the industry standard logout message format that fix provides at the given time.

About your point on rest, I do acknowledge the difficulties you're mentioning, of every broker requiring different rest messages to do the same thing. I've come across brokers which accept single orders and grouping in different messages. The delay and errors it causes is insufferable.

The problem is, there has not been a body enforcing unity across brokers. Fix is a nice try, but it is left alone in the woods without any restrictions as to what brokers can or cannot alter. I would like this pointed out and heard of more and that's it.
Even if std::2018 is just doing: `pub use std::2021::Option`?
Where do academics put their material nowadays?
A Promise of a Bright Future with Async Iterators, Generators, and Pipes, Part 1
I see, thanks for the explanation. Oh well, let's see where things go with Vulkan compute.
This is precisely the idea of liquid democracy: https://en.wikipedia.org/wiki/Liquid_democracy
I have typed my website URL wrong. How do I edit?
You can also skip building, and run directly using `go run`!
~17 USD/trade? Jesus christ that's high..
Me too, but I also feel it’s wrong to ask. And really it doesn’t matter, it’s better not to know as then this post is more applicable to people in the same boat across all diseases the average person doesn’t understand
As a Go programmer myself, the syntax of Go is simple yet effective. You are in control of what should be done, and Go will make sure all edgecases are covered in _defined_ behaviour like a managed language would. In C, reading out of bounds is legal (except when the address is not accesdible). In Go, you will get a panic (that you can still catch, but its pointing out an invalid program state).