skysight-inc/HackerNews huggingface dataset:
Telegram has been developed by Pavel Durov the founder of the russian social network VK. It was infamous for storing user passwords in plain text and many other data privacy issues. So his track record when it comes to data security and privacy is really bad. I wouldn‘t trust any software developed by Durov. Security and privacy is simply not important to him. This makes Telegram very unpopular at HN.
I think a better employer only looks at history insofar as it's a predictor of future potential. Gaps in employment history that relate to personal challenges, be they medical, family related, or motivational, shouldn't be seen as black marks as long as they're resolved and skills are current. People may have grown during these periods more than you might think.
Just do stuff. The world has a lot of terrible problems and being in your unique position, you could start to tackle those that are close to you. Eg,climate change,public transport, homelessness, hunger, etc.
E.g. If I had that kind of money and time, I would buy up land to do build a vertical farm and research hydrophonics and aquaphonics as replacement for traditional farming.
This and the "Gentleperson's Guide to Forum Spies[0,1]," obviously a troll post from 4chan or somewhere similar given the language, which basically takes the normal activity of trolls and internet argument and tries to convince the reader that it's all the work of government agents.

Great way to stir up paranoia on a forum where people tend not to be able to grok humor, but also tend to believe in conspiracy theories.

[0]https://cryptome.org/2012/07/gent-forum-spies.htm

[1]https://news.ycombinator.com/item?id=4277278
Best JavaScript content for November 2021
Sorry to burst this bubble, but all 3 languages you mentioned won't lose any space for Rust for backends. Rust can only dream to come close to have tooling as nice as C#, Go and Java. Productivity wise, Rust is just not as good as the other languages you mentioned.

async on Rust is a pain in the ass. For your hot path, sure use Rust, otherwise no one cares about a GC language as long as it's productive and can get the job done faster.
I use ublock, which does block the script, and run into issues occasionally because of this. It seems to be mostly an issue with shopping carts.
Resplendent!
> Terminators nominally make warfare more palatable than nukes, cruise missiles, or tanks & artillery

I guess I’d want to see evidence for this before pursuing an international moratorium everyone will undoubtedly violate the second it’s signed. Remote fire doesn’t seem that much closer than remote kill authorisations.
And it sounds pretty biased too. Sure, in Go (and other garbage-collected languages) you have less control over resources and memory, but you know what? Sometimes you don't want to worry about resources and memory! And, for most real-world applications, the small performance hit caused by not having this total control is more than acceptable...
The exception I was thinking of was carefully vetted other people wealthier than you who can act as a mentor and intro to connections
What about government/municipality data?

We paid for that once, surely it shouldn't be necessary to charge for it again?
> there is complete consensus on not wanting a world dominated by killer robots.

That and nukes. It is ok to not want these things, but to survive as a nation state, these things will become necessary developments in order to survive. If GP is correct about some of the capabilities we're likely to see, then any nation state without these will need to begin development in order to ensure survival. Is that an arms race waiting to happen? Yes. Is there a better way? No. The alternative to an escalating arms race is actual war.

We will never be done with power hungry ideologues, we will never be done with Communists whose sole mission is dominion over the whole world, we will never be done with petty despots (looking at you, Putin) who so wish they could play a meaningful role on the world stage. All of these have every reason to develop a new super weapon to tilt the balance of power in their favor.

Iran, for example, has started its centrifuges again. They also have some new ones that spin at 10x the speed of their old ones. They are very close to possessing a nuclear bomb. Up until the end of the Trump presidency they had halted production of uranium and talks were going well. Biden has about the weakest foreign policy of any president in the last half century.

Part of that effective foreign policy is the military might the US has. (Why do we have 5 carrier battle groups? Why does Britain only have one? Why does Russia have a single carrier that's in rather poor repair?)

If killer drones are an effective war-fighting tool (an it appears they are), they are inevitable. What we need to ensure is that they are used as humanely as possible.
Looks similar to what an E4 / E5 individual contributor makes these days at GitHub, based on Levels.fyi data (which usually seem right): https://www.levels.fyi/company/GitHub/salaries/Software-Engi...
Except they aren’t cheap at all (even if they should be) and the defence contractors building them aren’t exactly doing an awesome job for all that money.

Remember this? https://www.wsj.com/articles/SB126102247889095011
Which is why I look forward to spending the send half of the 2020's writing WASM by hand that gets JIT-compiled into machine code and then executed in the best implementation of Hypertalk I can get my hands on.
So basically you don't even value your own life? Is that really the basis of your argument? You don't even try to argue "More deadly weapons are not neccessary for our survival," you just straight up concede "I'm OK with losing the war and having everyone get killed." Good for you, but the rest of us want to survive.
Most humans ever born, are still alive today. Our population growth over the past centuries dwarf populations of the prior centuries.

Please explain how you get to this conclusion. It makes no sense.
I'm sorry. That was an awkward way of saying it that I didn't notice until you pointed it out.
I really enjoyed the book (although I read when I was well beyond the recommended age group). I wrote about it a while ago [1], and I think it can be still valuable for someone in their 30s (or, if you have kids, it will be valuable for them one day).

[1] https://www.quora.com/I-am-in-my-late-20s-and-feel-I-have-wa...
ASCII actually had up-arrow instead of caret before 1967/1968, although that was slightly before the birth of Pascal (published in 1970).
What part of you says it's a lot of money? I'd indulge some of the commenters here and try an experiment: tell yourself that it's not much--at least not enough to call yourself "wealthy" or "rich"--and see if it changes your perspective on the problem. Find a way to unburden yourself from the money by not identifying with it.
Bike Index is very well known at least in OR/WA (I'm in PDX) and has been around a long time. I appreciate you're supportive of another effort but you don't need to push one effort down to lift another up.
You do the arm signal for drone swarm, shout "drones, drones, drones!", and drop to the ground and cover yourself in your poncho.

My point is that we adapt. It's not worse than chemical weapons and it's preferable to bombing entire cities to achieve your objective. Is it finally dawning on HN that war is hell?
I suspect the same re: this library: IO is indeed too broad, and a logging system needs to do IO.

You could use other monads though.

> Haskell similarly suffers

Haskell practitioners aim to write as much code as possible outside the IO monad. If everything you write lives inside that monad, what's the benefit?

The nice thing about Haskell is that if you write every function with IO in its signature, it's bound to raise eyebrows in code reviews, whereas in most other mainstream languages everything lives in an IO monad by default!
> I mean to give credit, it’s hard to provide a universal opt out as it can’t be buried in account settings in some profile somewhere (the end user may not have a google account). Technically speaking, how do you opt out of something that is both invisible and universal?

Respect the Do-Not-Track HTTP header and never generate the return response.
I've had aphantasia all my life, although my dreams are still visual, as though they're real.
The article claims it is more common among academics and computer scientists, so perhaps it's fairly common here.

Perhaps it's helpful for dealing with abstraction, as abstractions don't always map well to visual representations.
ClearBit and Plaid haven't been mentioned yet – both examples of multi-million/billion dollar business built on the back of scraping.

The more specialized you can get the better chances of success imo. Generic web scrapers are dime-a-dozen
No.

There are many reasons that even ordinary people should, in my opinion, read such material and take it in, but the most important one is that understanding how other people work is necessary to knowing if you are being manipulated and how to out-manipulate the manipulator if that's called for.

Of course, I think if I didn't include the 48 Laws of Power, attributions of sociopathy towards me (yours certainly not being the first) would be largely diminished. Cialdini's books, if you were to read them, certainly aren't written as guides on how to be a sociopath, but rather the contrary. The 48 Laws of Power is written the way it was to be the most entertaining and thematic, which I think is pretty clear.
At least this one is "only" denial of service and not another RCE?
That's gonna really depend on the monitor, of course. My 46" 4K, that'd be on the floor. :-) But, I've had pretty good luck with keeping my monitors lower, and I tend to have issues with dry eyes.
There are many biased yet interesting blogs and talks about how Rust is the future of programming for domain XYZ. This article is not one of them. Breathless 90's-era posts about how Java and OOP will save the world look tame compared to BS contained in this article. I don't think this kind of argumentation is good for Rust or its potential users. God save the poor souls who are forced into Rust for no reason other than their CTO stumbled upon this article and was convinced of the hype.
Core Transformation by Connierae Andreas ($3 on kindle)

on transforming core motivational schemas that we were conditioned with since a young age and no longer serve us

Opening the Heart of Compassion by Lar Short and Martin Lowenthal (available free on dli.org)

on understanding deep patterns of behavior in yourself
Do you have an example for minutes of compile time for a single line? Especially since 1.6 (march 2021), I haven't run into that (and I'm using Julia pretty much full-time).
People think of terminators when they hear killer drones, but the cat has been out of the bag for a long time. We've already had Killer Robots for many decades.

It started with icbm's in the 1950s. More sophisticated platforms like the US the US tamohawk missile have been around since the 80s.
I don't see where I said anything disparaging bikeindex, it certainly can't hurt to register a bike or search on both sites. My comment was a one person sample size anecdote of what I've commonly seen used on the west coast.
"Python" as in "SymPy"? Was the translation actually equivalent? Did you try Compile[]? [1]

[1] https://reference.wolfram.com/language/ref/Compile.html
Was there a point to that wall of text? If so, what?
> In the past 5 years there’s been 1 rust job in my region of Denmark. It listed rust as a “nice to have”. I think it fares better in the Copenhagen region, but not by much.

This is pretty much what killed me on it, and I think the leadership and community really don't understand that commodity development is important to language growth.

I like Rust and it opens up some interesting domains I don't get to play with much, but it's a considerable effort to learn it when I know there are zero real opportunities to use it professionally. I keep hearing hype about how this or that big giant company is using it, but none of them are hiring for it: it seems quite a few are just shifting internal C/C++ teams to Rust. The rare public openings are either a) demand extremely senior C/C++ level dev experience, or b) vague crypto/blockchain startups that reek of fly-by-night scams.

Far from the hope of "democratizing" systems programming, it seems like the industry has instead closed ranks around it and used it as a further gatekeeping tool to keep out entry or even journeyman level experience, and certainly anyone not already bathed in the old C languages.

I thought Rust was supposed to free us from C?
Humans are monkeys: there’s no way to draw “monkey” that doesn’t include “ape” in its clade.

But yes — chimps (and bonobos) are our closest relatives.

https://en.m.wikipedia.org/wiki/Hominidae#/media/File%3AHomi...
I've been reading Mary Roach's new book (Fuzz) that has an interesting chapter on monkeys in India. Because macaques are afraid of langurs, some people would tie up langurs outside their houses for security. This was eventually deemed inhumane but it probably still happens in wealthy enclaves. Nowadays the Parliament building is protected by 40 humans who imitate langurs.
A bit too fanboy, perhaps.

After over a year of Rust, writing a client for a virtual world, I'm moderately happy with it. But not uncritical.

- The safety system is quite good. I haven't had to use a debugger on my own code. The one time I needed a debugger, the problem was unsafe code in a library I was using.

- Some kinds of data structures are difficult in Rust. Rust tries to be a functional language, sort of, in that it favors move semantics. If your problem really does involve complex in-memory state (I have a big 3D world to manage) there are substantial pain points. The lack of back pointers is a big problem. It's possible to work around this with reference-counted forward pointers and weak reference-counted back pointers. But the borrow checker doesn't help with that, and you can fail on double-borrow or double-lock situations at run time. When that occurs, it usually means a sizable redesign is needed. What's needed is single ownership with safe back pointers and compile time checking. This is a tough theoretical problem, because you have to prevent double mutable borrows by static analysis, but some people are thinking about it.

- When you've painted yourself into a corner in data structure design, it's often tempting to use "unsafe" to get out. I see too much of that in libraries. I don't use "unsafe" at all in my own code, and now and then I have to go and rewrite something to avoid it.

- Rust is overkill for many applications. Especially web services. For most web back-end stuff, Go is easier. Go also has all the libraries for web back-end stuff, mostly written and used by Google. So they're well-exercised and debugged. Also, goroutines, which are lightweight but preeemptable, avoid the problems of "async", where you have to be very careful about not being compute-bound for too long.

- After a lot of churn in the early years, error handling seems to have settled down to something reasonable.

- The "async everywhere" crowd needs to be restrained from making "async" mandatory in libraries. Their model is mostly applicable to web back-end systems where a large number of slow concurrent sessions have to be handled, those sessions don't interact with each other much, and there's not too much compute-bound work. Not everything is web back end.
Java doesn't integrate well with Julia, but Julia's interop with C++ and python are both pretty painless. pycall in particular is about as easy as you could imagine.
An SVG blob generator with extra controls
World News at a Glance - bloat-free & JS-free
> nah, CIA’s greatest trick is making people look over their shoulders, sabotage themselves through paranoia.

My impression is completely the opposite. The CIA itself is a large inefficient bureaucracy and the people who wrote this are clever operators who have seen this in action themselves and can now point to this to accuse the perpetrators of being enemy saboteurs.

Think about what the countermeasures against this look like. Fewer bureaucratic rules, less rigidity, smaller teams, more individual autonomy. The behavior of the intransigent bureaucrat and the saboteur are the same, so institute policies in the name of defeating the one and you also take care of the other.
>> One of the biggest issues that are plaguing the developers are memory management issues.

> ...not an issue in any garbage collected language.

I pretty strongly disagree. It’s less of an issue in strongly typed languages but definitely null references and (arguably) type/encoding runtime errors are memory management issues much more common in garage collected languages.

What I love about Haskell (thousands of hours) and to a lesser degree rust (hundreds of hours) over most languages is that they are very expressive while at the same time the compiler catches what feels like 20x as many mistakes as I’d get from python or modern JavaScript.

Then it also runs faster, on a smaller footprint than most other stacks.

Both Haskell (and to a lesser degree) rust are much harder to learn than python/ruby/js but rust is probably on-par with c++ or java.
Relevant article from Texas Monthly regarding the history of Osage Orange:

https://www.texasmonthly.com/being-texan/osage-orange-histor...
My first job as a teenager was writing Perl scripts for what I now realize was a phone marketing company. I would do things like process phone numbers and replace area codes with newly added area codes depending on the other digits and process data from contacts to produce a list of phone numbers that the other employees would then call in order. I don’t recall much but I do know Perl was a joy for text processing, much easier than anything else I’ve used for that today. That was back when you needed the big oreilly books to lookup for to do things, before Google was useful for that.
"The City Council cut the LAPD by $150 million in July, after massive protests following Floyd’s death, pledging to put the proceeds into disenfranchised communities. Council members quickly set aside $60 million, using much of those funds to balance the budget, leaving about $89 million for various programs."

L.A. cut millions from the LAPD after George Floyd. Here’s where that money is going

https://www.latimes.com/california/story/2021-05-26/lapd-fun....
Well, wrte it to whom? No legal structure is what the comment was partly about.
This problem with the scala community exists because it is composed of two different philosophical schools of thought. There's the ML camp, which is where we get all of the awesome pragmatic features of the ML family of languages (Martin Odersky has been very clear that Scala is philosophically an ML-family language).

And then we get the Haskell camp, which rightly determined that the Haskell ecosystem was terrible. But instead of adopting an ML mindset of pragmatic functional programming, they decided to bring along their puritan religiosity with them and make the Scala ecosystem terrible too.

The funny thing about Scala's pure functional programming ecosystem is that in its quest to make all programs pure in the sense of not having side effects, they pollute the entire ecosystem with hordes of incompatible dependencies, which need all sorts of bullshit adapters to make them play nice with each other. A far cry from what most people think of with the word "pure".

To quote one of the best essays on the ML philosophy:

> My point is that the ML module system can be deployed by you to impose the sorts of effect segregation imposed on you by default in Haskell. There is nothing special about Haskell that makes this possible, and nothing special about ML that inhibits it. It’s all a mode of use of modules.

> So why don’t we do this by default? Because it’s not such a great idea. Yes, I know it sounds wonderful at first, but then you realize that it’s pretty horrible. Once you’re in the IO monad, you’re stuck there forever, and are reduced to Algol-style imperative programming. You cannot easily convert between functional and monadic style without a radical restructuring of code. And you are deprived of the useful concept of a benign effect.

https://existentialtype.wordpress.com/2011/05/01/of-course-m...
Read Bhagavad Gita - there’s a great audio book and if you grind through the first couple poetic chapters, it’s amazing.

It talks a lot about the concept of selfless action (karma yoga) and why this is the best mode of operating in this universe. A concept fairly foreign to capitalistic societies :) But now since you are out of the grind, you can actually just enact as much positive change as you’d like and enjoy the process.

Like assemble a crew and go build infrastructure in a poor village. Or save animals from poachers (animals and wild nature are dope overall). Build a mushroom retreat in Portugal or Costa Rica (btw check Santa Teresa for sure).

You have a life of wonders ahead of you. You just need the right perspective (less I, more other living beings).
I am still in doubt about this being revenge. I'm not necessarily saying it isn't, but doesn't culling the dogs as a means of pest control also fit the hypothesis? I mean, if a baby in a human town was bit by a rat, we humans would react by trying to eradicate the local rat population. You could call that revenge I guess, but normally we wouldn't ascribe such a passionate motive to our behavior, we would say it was logical to eliminate a source of danger.
The Smalltalk syntax is pretty esoteric, but even if you become used to it, the fact that it requires all parameters to be named makes it an exceptionally verbose language that takes longer to parse in your head than most.

I much prefer more modern languages that allow you to explicitly name the parameters when you need to, but other than that, never requires it (e.g. Kotlin and Swift).
Adidas sells first NFTs, limited to 2 per person. One person bought 330
Text adventures are perfect for that.

Get Winfrotz for Windows or Lectrote under Linux/OSX and download Anchorhead, Spider and Web, Make It Good, Vicious Cycles, All Things Devour, Enemies and Slouch Over Bedlam from IFDB, they should be in Z5 or Z8 format. "Heroines" and "Enemies" are good, too.
I like how much the compiler helps me. I find it to be a tax on my productivity for about the first 1500 LOC of a project, but once I get beyond that, the compiler is an indispensable aid for refactoring in a way that Python’s type system (even with annotations) just isn’t rich enough to enable. For example, if I add a variant to an enum, my editor will immediately show me all the places that variant needs to be handled.

I find cargo more productive than Python’s package management, where I have to manually manage environments and requirements.txt files.

Things I like less: less “batteries included”, so I spend more time evaluating libraries and wondering if a github project hasn’t been touched since 2019 because it just works, or because the maintainer got bored. The learning curve is steep at times, and involved being blocked on pleasing the compiler.
Discussion is ok. Disrespect is not.

What original sin? What fault? You’re basically saying that log4j developers lured you into temptation, otherwise you would have coded your own logging library, which, for sure, would have been better.

I haven’t seen 1/100 of this hatred for Apple iMessage vuln that led to NSO zero-click exploits, and I don’t get why.
There is also https://github.com/valskalla/odin for a pure/fp Scala logging library (also includes a slf4j bridge if you need to work with java stuff)

It also has some "fancy" features like changing log level if exception happens

https://github.com/valskalla/odin#extras-conditional-logging

Though we have not yet upgraded it to Scala 3 it should work with Scala 3 just fine. (We do compile a Scala 3 release of most of the stuff but the codebase itself is mostly Scala 2 for now)