skysight-inc/HackerNews huggingface dataset:
I worked on that a lot (though the native format was XML, don't shoot me) ages ago and ultimately put it aside as any kind of language that is visualized from some format meant to not be read directly has to deal with the issue that you still need a canonical textual representation for communication outside of the tooling. Someone e.g. will copy and paste their esotheric view of the code into Slack or an email.

It's a complex problem. There is a lot of interesting design space to explore there, but that issue needs a solution.
What was the original recording? I assume much would be 1/4 inch tape off a nagra with a decent microphone but given how much was in studio it could be full 1inch tape, kinda like a wild track left running.

The biographies says the Beatles hated stereo right up to the end. But they did like high quality recording.

(I got to play with a nagra in the 80s. It was wonderful)
That‘s why you generate a new key pair for every service.
Should we rein cities in or embrace their biomorphic potential?
And build a simple system that doesn't directly forward messages to each recipient outside their specific working hours. Thus, your colleagues halfway across the country may get your message immediately, but those halfway across the globe won't see it until they get to work again.
Oh man such as a sad and predictable course of action by Rockstar and Take2.

This could have been a great moment for them to acknowledge and praise their fans' decade-long dedication to one of the most recognizable franchises out there and they ruin every aspect of it.

Needless to say, not gonna buy that lazy-ass remaster. Sort of reminds me of the equally lazy Mass Effect "legendary" edition.
There are constant efforts to make async easier in all languages. It'll never be as easy as writing synchronous code.

I really don't like futures/promises, I don't know where this abstraction came from.

Callbacks are where it's at. Someone, somewhere has to write callback code; they cannot be got rid of. What works for me is keeping the callback handler as short as possible, this usually means just pushing 'work' onto an async queue that is serviced by one or more threads.
Radio waves in a vacuum travel at c. They move more slowly in things like copper. Light in fiber cables travel at about 2/3 c so a neutrino beam would be faster and potentially have a shorter distance by going through the earth. Actually designing and implementing a communications system using neutrinos is an exercise left to the reader.
It’s impossible to know the best approach without understanding the specifics. It’s true that adding more resources quickly when you own the hardware will take more, but given how much cheaper it is, you can seriously over provision. Using aws is probably going to be more efficient usage of hardware, that’s why it’s not even more expensive. The thing is that it’s often not the more efficient use of money, specially at that scale.
>so it could potentially survive impact with water and be recovered.

Doubtful even if pointy. Water is way denser than atmosphere
How to beat Amazon with your E-Commerce company
Yes. It is very easy to accidentally produce denormals in recursive audio algorithms.
The hydration thing, I just got into the habit of dropping my soluble vitamin in a pint of ice cold water every morning and downing it then drinking normally through the day.

It takes a while between drinking and it having an affect (variant on numerous factors) but I found the morning fog within an hour of waking up was much reduced just by drinking immediately on waking.
And you still run into all sorts of ergonomic issues when you inevitably need to dereference your Rc<> pointer. That said, I sympathize with the parent's desire for a proper Rust-lite with a GC: C-family syntax, great tooling, great documentation, great standard library and ecosystem, native+static compilation by default. Of course, someone will ignore those criteria and come in suggesting OCaml/Reason...
> GC pauses, Rc<T> does not, it's simply a deallocation by the last reference holder

While the last bit is true, it may actually end up having to do lots of work. Think large object graphs where the last reference to any of it goes out of scope.

Also, as a matter of terminology: Rc is a form of garbage collection. It's also a pretty bad general GC strategy at that -- which is why one doesn't just slap an Rc on everything.
Also if you are writing a document, it's much easier to just give it a high classification to be on the safe side than try and figure out what the lowest classification it could have is. And as everybody you are working who will need to read it will have clearance anyway, it won't make it any harder for those people.
Accidentally Causing a Switch Rumor
I haven't worked through the book yet but looking at the authors, Yaglom wrote some great Math books and Zeldovich was an absolutely genius in the field of theoretical physics, so it probably is.

As a German living in the Western part, my math teacher would always rant how much better the East German math books were. Math and science education in the Soviet Union and the Eastern Bloc was and still is vastly superior to anything we had or have in the West.

See also this thread:
https://news.ycombinator.com/item?id=26849866#26850468
What attack vector do you think this would mitigate?

You'd need several prerequisites for that to actually increase security, i.e. not using an ssh-agent (required password for every key prompt) and encrypting them at rest

Otherwise you'll leak all your keys as soon as any attack vector is utilized such as hostile host siphoning from the ssh-agent forwarding or filesystem access.
There is no direct path through you unfortunately and even your parent (her son/daughter) couldn't petition for her unless your parent was a US citizen. What's her country of citizenship and what's her educational and employment background?
I think it's not entirely fair to paint problems with rust's async features as an aversion to low-level-ness.

If anything, I think the issue with Rust's async is that it tries to be too high level.

In my experience with async rust, most of the difficulty comes from "spooky errors at a distance". I.e, you're writing some code which feels completely normal, and then suddenly you are hit with a large, obtuse error message about types and traits you didn't even know you were working with. The reason being, something went wrong with all the inference involved in implicitly wrapping everything in futures. And often it's not even related to the line of code you just wrote.

So in these cases, I think the issue is that rust tries very hard to wrap async in a very smooth, sugared syntax. It works fine in a lot of cases, but due to the precise nature of Rust, there are a cases where it doesn't work. And because the system relies on a lot of magic inference, the programmer has to hold a lot of assumptions and rules in their mind to work effectively with async.

I am not an expert, but from my experience it feels like async rust was a bit rushed. It should have been introduced as a more explicit syntax first, with sugar on top once the guard rails had better been figured out through experimentation.

That is under the assumption that future-based async in rust is a good idea at all. Rust's ownership model becomes intuitive very quickly in the single-threaded case, but at times it feels like a square peg in a round hole where async is concerned.
That is what I was looking for, what information, present here at this site.

https://www.skylightpaycard.me/
If you expect them to be safe, you're in for some fun!
Ask HN: How many letters autocomplete to this site in your address bar?
For example, for me it's two, very fittingly 'h' and 'n'.

When I type either one into my address bar, the first autocomplete choice is this site.

(The 'h' is for https, which says a lot.)
Bottling-up anger is unhealthy and exploding is unprofessional. Inform them of thoughts tactfully in real time, whenever possible.
Android LottieDialog 1.0.0
Android Library to make it easy to create custom dialogs with lottie animation view
If you managed to crack the detection problem, you’d still likely be so saturated with solar / background neutrinos as to confound any real prospect of a signal.
> We call ourselves “Developed”. It’s already implicitly throwing in the towel - there is nothing more to be done. We’ve already developed.

I don't agree with this take. The terms "developed" and "developing" is just a politically correct term to classify countries based on their industrial base.

https://en.wikipedia.org/wiki/Developing_country

It's use has less to do with developed countries and everything to do with the need to frame the issue as countries working to get where others already are at the moment.

> This entire thinking and it’s psyche in our society feels like straight up propaganda. It used to be first-world and third-world.

I also don't feel you're right here as well. "Third-world" does not refer to a ranking. It was a classification based on where a nation was with regards to the Cold War. Either they're a NATO and NATO-aligned country, a Warsaw pact and USSR country, or you kept yourself out of the cold war and thus were a part of the third world.

https://en.m.wikipedia.org/wiki/Third_World

Development and industrialization and economic output had nothing to do with it.
A RasPi-quality Linux experience with the compute power of something like the Snapdragon 870 or Dimensity 900 [1] is what I am envisioning. Those chips are available in phones with fancy case/battery/screen/cameras for ~$250. [2]

I just want to trade that for some IO and Linux support.

1: https://nanoreview.net/en/soc-compare/qualcomm-snapdragon-870-vs-apple-a15-bionic
2: https://www.kimovil.com/en/where-to-buy-vivo-iqoo-z5x
Do you think PR agencies don't maintain such accounts?
Absolutely, it's done all the time. They would come here as business visitors with B-1 visas or with their passports if they are from a visa waiver country (such as the UK). But so there are no issues and no lines are crossed, when they are in the US, they shouldn't be compensated (paid their hourly rate, for example) although their expenses can be covered.
One for 'n', but 'h' tries to go to "healthfully.com" which I've never heard of. Firefox 94.0.1.
>Honestly, hiring a "head of growth" sounds like more trouble than it's worth.

Hence, the purpose of the article which is to sell you their services as part-time growth writer promotional consultants.

>Massive incentive to bullshit

You're not kidding, this is a significant component whether you can really deliver or not.

I wouldn't do this unless I could deliver certain concrete results with outstanding upside to boot, but regardless there would be some need to BS your way in to begin with.

Actually I would do this but I would have to divert effort into interfacing with the BS in addition to the usual workarounds. Ugh.

If it's actually impossible to bring a completely BS-free promise/delivery cycle every time, realistically more visible progress could probably be made in orgs where the existent BS is already huge by comparison.

>they do actually grow your business
>you've taken all intuitive understanding of how your business works and embodied it within someone who can leave whenever they feel like it.

>Unless the founder plans to hit the eject button

A good plan would be to establish significant growth momentum early on, then try to increase that if possible, in a way that whatever momentum achieved will remain after that growth instigator may no longer be in position.

Either way, with that in mind I think the right idea for me would be to dive in full-time and make maximum progress every day on the biggest low-hanging fruit, then move on to the next location. I would be leaving when I felt like it but that would be with major milestones left in place and the feeling of a project completed by all.

Plus OTOH from a corporate point of view when the time comes they should be able to change heads of growth more easily than other executives when they feel like it, since different extreme-growth operators can have very different strategies. And of course there's that BS element which should dissipate not accrue.

>the whole company is about growth. The entire team is responsible for growth.

This is usually not implemented as thoroughly as it could be.

>It's far better to invest in infrastructure and building muscle in the entire team around growth

This is what a growth leader is supposed to have the resources and authority to do; build a stronger foundation so that striving to the next level can more realistically be achieved while everyone else is already busy maintaining the degree of success that has already been accomplished.

>too much growth and not enough profit/endurance? Anybody can grow a company 500% a year if they're willing to lose a billion dollars

I think of that more like "expansion". Growth as a result of increasing profits is in a different category.
> I love Rust precisely because of this. You can leverage the compiler to drive your development and design. If it's hard, then it's probably wrong!

Yes, I had the same experience writing code in Rust and Haskell. If the design works nicely with the language, then also the design is better, more modular, simpler dependencies and easier to understand and extend.
IDK if they can make it work on Earth, but the Moon would still be valuable - and with zero atmosphere to slow things down.

Production of chemical fuel on Moon is going be tricky, there are no fossil fuel deposits there and water is much scarcer than on Earth. Our contemporary chemistry isn't completely ready for such conditions, at least not on industrial scales.

If we could use a mechanical / electrical mechanism to throw things onto the Lunar orbit, it might be much more efficient than, say, making methane in situ using Sabatier reaction. Solar panels are much more productive on the Moon than on Earth.
> America has never been a champion of immigration

97.91% of US citizens have immigrant ancestors, if that's not championing immigration nothing is.
Couldn’t #2 shaders be compiled once and shared between users? A game could compile them on first run, submit them to a server with a unique hash of the OS, driver and shader version (and what else). Then other users could download the already compiled shaders if there’s a network connection. If not, you simply compile them anyway.

If security is an issue (can a shaders be dangerous?) you could wait until you have X copies of the same hash and verify that they all have compiled to the same code before adding it to the online cache.

Developers could even pre-compute such shaders for popular GPUs that they have access to.
Sure, it's possible to parametrize your algorithms.

However, do you need to explicitly parametrize them or does the language do it for you? I'm not aware of any language that would remove the need to consider them and just automatically "work" with async types whereas "normal" threading—with errors handled via exceptions—more or less work out of the box the way you expect.
Wish I understood this better. Seems very interesting.
He documented this plan already in 1990:

> At the time of my death, it is my intention that the then-current versions of TeX and METAFONT be forever left unchanged, except that the final version numbers to be reported in the “banner” lines of the programs should become

> TeX, Version $\pi$

> and

> METAFONT, Version $e$

> respectively. From that moment on, all “bugs” will be permanent “features.”

(See http://www.ntg.nl/maps/05/34.pdf)
While I understand that with Graal and .Net you can ostensibly make native, static binaries for Kotlin or C#, I'm very skeptical that it works well in practice. In particular, I'm guessing it will feel like swimming upstream, fighting an ecosystem and build tooling which mostly assume you're running on a VM. And then there's the question of performance...

And of course, with Python your code will run 100x slower than either of the above, your dependency management will suck, you won't be able to statically compile, and to top it all off everyone will give you recommendations for your ailments which take a long time to try out and inevitably will fail miserably for one glaring reason or another. By way of example: "just rewrite the slow bits in C" -> you rewrite the slow bits in C -> your code is now slower because the marshaling costs exceed the gains + your build system is dramatically more complex and you have the sheer joy of debugging segfaults and undefined behavior (yeah, I know Cython exists).
Overdrafts are very much a thing in the UK, most accounts allow it, but you have to request it in advance. In effect they work like a pre-approved loan, which at least when I was working badly paid jobs and needed food right up before payday was a very welcome feature.
The material had been transferred when I started working on it - but as I understand it, they had 2 x Nagra 1/4” machine running pretty much continuously. The cameras were filming sporadically and not all of the audio tapes had been recovered.

My job was a gigantic jigsaw puzzle of watching the pictures and reuniting it with the correct sound for the first time since the original movie.

Nagra made some amazing machines - such incredible precise engineering.
I had a different concern... if people eventually start to use SSH keys to sign git commits, (as the article suggests will soon be possible), people can't validate github commit sigs with github public keys directly at one point in time... because if one is compromised, so is the other.

The only way github could be used as key distribution for this purpose would be if individuals take (and keep) a copy of every public key they are interested for future verification in-case an attacker changes it. But then I guess any public key distribution system has this problem??
C code is of course close to the hardware, which as always, has benefits and drawbacks.
There is a version with an English voice over of the original talk here:

https://youtu.be/zXXmhxbQ-hk

And the talk he gave in English himself here:

https://m.youtube.com/watch?v=c0O6UXrOZJo
This seems, pretty easy to fullfill technical wise.. just store the work-messages in dbs and trigger the send, when the person switches the app into work-mode.
When that happens you were relying on security by obscurity. It’s a hack waiting to happen. This, at least creates awareness and forces secure keys. But you are right, it may be a security risk, but only when it already was (arguably it was smaller).
There's no issue with moving from a TN to a green card; the process just needs to be managed carefully and all this really means in the end is coordinating the timing of the filing after deciding on the green card path (that is, whether through USCIS or a US Consulate).
> subversion barely tracked merge history at all, which made it easy to end up with bad merges after accidentally merging the same change multiple times

Weird. Shouldn't that be just a no-op?
Look closely. The first half of the letter on each line is faded. (I'm the refering to the pages of the book, not the pages of the PDF)
> Something that China had been pushing for years now…

Given the source and the target of said message, it reads like a mob-like "you have a nice business here, it would be a shame if something happened to it".
It isn't but it probably should be. We just don't do enough.
On the other hand, how much broken code has been fixed to properly deal with paths just because of that? I'd argue that to be a major benefit. Same with Windows Vista forcing developers to write applications that work properly as a non-admin user.
Jetpack Compose: Tabs with Swiping
You can avoid specifying a lot of parameters at each SSH connection by defining aliases, e.g. of the form ssh-servername.

In each alias you put the appropriate "-i private_key_for_that_server", the server name and also "-l user_name" if you have a different user there and "-p port" if the server uses a non-standard port.

Thus, after the initial key setup, connecting to any server with different credentials is no more complex than when using a single key pair.

Except for an extra keygen step, the initial setup is not more complex than when using a single key pair, as you have to copy the public keys anyway, which is the more difficult part of the setup.
I believe the parent wants to know how a sequence of IR instructions with alternating modes is translated to the target.

My guess would be that explicit state state changes show up in the generated machine code.
Yes, there are paths to working in the US (and ultimately getting a green card) through your own business. Depending on the facts, the typical visa options are the E-1, E-2, and the L-1 and the typical green card options are EB1 extraordinary ability and EB2 national interest waiver.
I'm talking about keys that have certificates issued by authorized centers. Those keys have legal power. Also obtaining a certificate costs a fee.
Cool Sinophobia ITT
Heh, too late to edit :-/
Nice work, simple and easy to use!
I think there's value. Resources at the very least, be they from moons, planets or asteroids. The problem I have with space exploration is the cost.

Almost 10% of the global population still goes hungry, even though more than enough food is produced to feed the global population. That's 811 million people that starve while Bezos facilitates ego trips to space.
A list of cool podcasts, essays, interviews
Of course; because the adults are the advertisers. They’re trying real hard to appease the kids so they can sell shit to them.
I believe your speedometer is broken!
I think an important part of tech is continuously learning.

e.g. if you can't find jobs as a PHP developer, but you see there are many jobs for (say) NodeJS web development, or Golang API development, you may need to learn some things, but that can build upon how you did things with PHP.

You still have a website still involves HTML, CSS, and JavaScript. A website will still send HTTP requests (and receive responses). The program will still need to be deployed so that it's reachable from the web. etc. etc. -- And there will always be adjacent things which you will either need (or benefit from) learning.
There’s one final problem even harder than that. Creating a UI that by itself explains this whole complex concept, to a user with an average attention span of 3 microseconds.

Just look at how many scam attacks have been made possible just on urls.
im definitely not part of the past generation, but i get your point nonetheless. cs courses now are more focused on creating industry-ready developers than they are on creating solid academic programmers. in this sense cs courses now are much more vocational than they are academic. if we can agree on this difference between developers and programmers, then i still agree with the familiarity statement by the parent

also by the way, the recently released follow-up to SICP [0] is still in very much in lisp, MIT Scheme to be specific (like the original SICP). however, this book is far from an introductory text in software engineering

[0] https://mitpress.mit.edu/books/software-design-flexibility
Neat concept but don't see how they're going to get around the g forces.

Think about it...even a playground wheel can generate enough centrifugal/petal force to make a human feel a little unwell.

Non-trivial fundamental problem that you can't disappear by just inventing a new material/technique or something.
Biology and neurotechnology is where it's at. Neurotech in particular will make obsolete a large fraction of consumer tech. Electronic tech likes to pat itself in the back for the incremental benefits of centralizing everything, but they forget that it comes at the cost of innovation.
That's a separate issue. If applying for a green card while in TN status, the timing of the green card application needs to be managed carefully if the applicant is applying through USCIS in the US and international travel needs to be managed carefully if the applicant is applying through a US Consulate.