skysight-inc/HackerNews huggingface dataset:
> simply encode those chunks on-demand

That's not always reasonable, though. If I upload a video at 4K, there needs to be some "baseline" encoding so that when the video is published, there's something playable without streaming 4K to, say, cell phones with a resolution smaller than 4K.

Even then, chewing on that 4K file into a 1080P resolution video "on-demand" for a desktop user on high-speed internet is no small task. First and foremost, you need to assume concurrency: if two people request the video at the same time, there's a complex problem of coordinating the encoding in a large distributed system so that the video is encoded once (or a very small number of times). You also need to do the encoding _faster than the video can be played_, or at least faster than the baseline/fallback version can be retrieved and sent. You also need to queue the next chunk(s) of video up, so you're not watching a chunk, buffering, watching a chunk, etc.

In a system at the scale of FB, it's not smooth sailing for compute jobs like this: you're subject to network latency, noisy neighbors, failures (disk/network/software/power/etc.). The case where you're able to stream the original file from storage, start encoding it and streaming the output back to storage and to everyone around the world who is requesting it _at that moment_, and coordinating the encoding of the next chunk is actually not very likely.

Want to talk about weird failure modes?

- I start watching your video and click all over the seek bar. Am I DOSing your compute cluster?

- Two users on opposite sides of the world request the same location of the same file with the same fidelity. Does one of those users get a dirt-slow experience, or do I double my compute costs?

- A thousand users start watching the same video at roughly the same time. A software bug causes the encoder(s) to crash. Do 1000 users suddenly have a broken experience, or does the video pause while your coordination software realizes there was a failure, releases the lock, and restarts that encoding job from the top while your users all get in line for the new job?

I'd argue that this is the _least simple_ approach. In the happy path, you get a nice outcome while reducing compute cost, and users get high-quality video. In the unhappy path, users get slow loading from slow encoding instead of reduced resolution, or you start to need to trade performance for compute (do you encode twice in two datacenters, or move compute further from the viewer?).
The size matter in my case. Above sample are only a portion of the actual data from multiple applications (sharing the same vm on cloud).
They are not for-profit projects so I'd try to reduce the hosting cost.

Maybe s3-style of storage is better than vm-harddisk in this case?

P.S. I'm storing the timestamps in millisecond
I default to https://www.diagrams.net/.

But I've used Microsoft Visio in the past and it's a really nice solution (this was 3 years ago, so it might be better/worse now).
I think similar issues would arise in space. I suspect living on a spaceship would be like being in prison
Xcode has aged very poorly and Apple top-level management refuses to invest further headcount into improving it in general.

They should port their custom tools like IB, view debugger, etc. over to Visual Studio Code and get out of the IDE game.
Yeah; my product team will get wildly different priorities over the course of a month as execs spin plates, PMs and managers scramble around, and we nail down what our next round of experimentation will involve. On top of that, relying on A/B testing for all decision making means you’re liable to discover at any point that there’s a totally different piece of software that you should have built instead.

It’s all chaotic, but I enjoy the scrum.
Mars helicopter achieves fastest, furthest flight yet
The media/intel community also pushed the likely bogus Russian/Taliban US troop bounty story really hard last year. But now all of the sudden they have had a moment of clarity:

https://www.thedailybeast.com/us-intel-walks-back-claim-russ...

Probably all just a coincidence though....
Thanks! It requires some planning.

It's been ~7-8 years, but I guess I probably figured out what trans-Munar injection velocity I needed and roughly what phase angle I wanted the Mun at (these are some basic astrodynamical calculations). You can determine velocity precisely from instruments and phase angle well enough from visuals that you pretty much guarantee a rendezvous.

Once you enter the Munar sphere of influence, just wait until periapsis and start killing velocity. You'll want a table prepared (somewhat conservatively, to give yourself room for fine-tuning) of what your velocity should be at a given altitude to make sure that you land at 0 m/s without using too much propellant, and remember to adjust the "sea level" altitudes for ground level before your radar altimeter kicks in. I guess the hard part is making sure you land on something flat, but you can impart some lateral impulse if necessary until you see a good landing spot below.

Getting back is similar, but the calculations are a bit simpler.
That's true. I did think about mentioning this possibility, but decided not to.

Another good example of predicting RNG, after a large amount of gameplay, for a non-turn-based game:

https://www.youtube.com/watch?v=1hs451PfFzQ

I think in certain Pokemon games, people figured out how to predict and manipulate random encounters based on an animation in the load screen.
Florida company reportedly took over a slice of the Pentagon's internet space
How exactly are they better from Kotlin's data classes?

Aside from the fact Java only released non-preview support for records one month ago, they:

- Don't support inheritance
- Can't be mutable
- Don't have a copy method

While Java records are nice, Kotlin data classes are strictly more capable than Java records.
They will never do this because it allows side stepping the app store. It's that simple.
Dlang (https://dlang.org) avoids all these mistakes through careful language design and compiler-enforced checks.
This is already not the best solution, there if you want “heroku style” then:
1. Install podman
2. Setup some container registry
3. Setup GitHub actions to build and push container
4. Setup podman for auto update
5. Push code and wait...

Much easier than hacking with bash and git.
Pushing source code to a remote server is bad!
I'd imagine restricting immigration would solve 99% of these problems. If someone wants to leave, then let them - it may just be hard to get back. If you have a place where the net desire is to leave, then you have problems that will not be solved by merely holding the passports of unwilling citizens.
Everything in an Airbnb or furnished rental is excluded. I do tend to wear sandals when it's hot, but think wool socks can still be comfortable in the heat if you get the light or ultralight versions. I am a minimalist and travel a lot from 2 home bases.
> I bet you don't leave much space for overpaying a foreigner if they are already getting 50% of what a local would get.

They are getting 50% of what a very senior dev would get.

They each make 4x the market rate for their country for this type of work (based on Upwork rates), which is 27x the average salary there.

> Regarding the criminal related comment, you should first and foremost trust and empower your employees independently of where they come from. And then you should also have controls in place to make it really difficult to steal your clients' money.

Thank you for the philosophy lesson. Do you have experience hiring people from many countries, or is this theoretical for you? It isn't theoretical for me.

What you are saying is exactly what I do. I trust all of my employees completely, but literally everyone who is betrayed made a mistake in trusting someone. I am not arrogant enough to say that my trust is 100% correct.

So how do I make it difficult for people to steal money? I rely on my country's law enforcement.

It is impossible to keep devs away from at least some sensitive data, like API keys. The "control" you're talking about is partly to hire people who have more incentive not to steal than to steal.
I agree with removing DMCA protections for circumventing DRM instead of outlawing or creating legislative disincentives for DRM outright (that would be a can of worms). However, it still doesn't sound like a full solution. Registration of the sort you propose, if done correctly, could work for e-books or movies. But what does that kind of registration look like for server- or cloud-based content (e.g. MMOs, subscription-only software) or video games that constantly get constant updates and DLCs?
An internet that is drastically less tied to surveillance capitalism, and where participants directly exchange value with each other instead of through privacy intrusions? Sounds perfect to me.
C++11 has been out for a decade now. Move semantics are not much more "recent" than Python 3.
Wanted: Principal engineers to drive AWS technical direction
Want to drive the direction of technology at AWS? AWS is hiring for principal engineers to work in the intersection of open source, observability, big data, Containers, data visualization and security. Drop me a message and lets chat. Referrals appreciated. You can also contact Jenafer Park on Linkedin or our leadership recruiting team at principal-engineer-hiring@amazon.com . Senior Principal, and Distinguished Engineers are Amazon's most senior individual technical contributors.
Amazon's Principal Engineer Community sets the standard for engineering excellence at Amazon. The community comprises Principal, Senior Principal, and Distinguished Engineers who are responsible for driving Amazon's overall technical architecture. Principal Engineers at Amazon are pragmatic visionaries. They make a lasting impact that echoes through the technology, the product, and the company. They work on Amazon's hardest problems, building high quality, architecturally sound systems that are aligned with our business needs. They remain hands-on and lead by example. By being close to the details, they earn the respect needed to be effective technical leaders. Principal Engineers bring clarity to complexity and demonstrate smart ways to simplify. They are leaders and mentors, setting excellent examples for their local teams and the entire Amazon engineering community. They meet regularly to question each other's assumptions, illuminate pitfalls, and foster shared understanding across all groups at Amazon. Learn more here https://www.amazon.jobs/en/landing_pages/principal-engineer-hiring
My biggest problem with trajectories in KSP was that they flip non-continuously once the trajectory passes through a sphere of influence. I believe it would be much clearer and easier if trajectories were continuously changing but just marked once they pass through a SoI.
> What we want is a diversity of perspectives, opinions, and philosophies toward life and everything.

If only...

My personal experience is that the folks who are most vocal about “diversity” (i.e., the letters in the passport you refer to) tend to be the least supportive of different perspectives, opinions, philosophies of life, etc.

“Agree with the way I think, or you are part of the problem” sadly is a common rallying cry.
The whole HOPL proceedings is worth reading.
Wasn't that decades ago? Times change and sometimes ideas are too new for its times.
TechShop's business model...

TechShop's business model was predicated on more investors coming in to fund growth, while the actual operations lost money. This didn't become clear until the financials came out during the bankruptcy lawsuits.[1]

The operating problem was that the "gym model" didn't work. Gyms thrive on members who pay but don't show up too much. Flat-rate maker spaces get customers for whom it's their primary workplace,
tying up the equipment all day. This reached its extreme during the Etsy period, when TechShop had 10 laser cutters making stuff all day.

[1] https://blog.adafruit.com/2020/01/31/latest-bankruptcy-court...
Kinda sorta. Yes, you a free to run off to anywhere in the world. Your passport protects you even in hostile countries. However, you are expected to return home and pay taxes. To leave the United States is an expensive affair if you want to truly leave by giving up your citizenship. To work abroad is expensive too if the foreign country has a lower tax rate. As a US citizen you are free to roam, but never to change your home.
Excerpts from different parts of the piece:

“I realised I was the only woman in the room,” she recalls, and describes a pang of exasperation. “It was like, of course I’m the only woman in a study about women’s bodies!”

And at that moment Pek knew they’d achieved something more significant than an arts project; they’d re-written around 500 years of anatomical assumptions.

It's actually really interesting stuff.
D's ownership/borrowing system does data flow analysis within functions, i.e. it's intra-function. Inter-function (global) is handled via the function signature.
New tricks for new years use free internet in USA by Zolaxis Patcher
> WesolyKubeczek

> I can’t understand why you’re being downvoted. Unless, of course, the HN crowd doesn’t like anyone putting spikes into myths it likes to perpetuate, like “installing Swift is involved on Linux”.

> Hello, it’s “dnf install -y swift-lang”, how less involved does it have to get?

> “Burn the heretic! It’s involved! I’d rather curl | sudo bash things all day!”

It seems like it's _officially_ packaged on only two distros which are relevant to Linux developers—Fedora, and NixOS https://repology.org/project/swift-lang/versions

It's also _unofficially_ packaged (aka by the community) for Arch via AUR, Slackware via SlackBuilds, and RHEL/CentOS via EPEL.

That's beyond pathetic, without even beginning to consider the resources of the company which backs them.

Take a look at how many distros Zig supports, for instance https://repology.org/project/zig/versions ...

...and Swift released the open-sourced Linux version roughly six years ago.
Maybe you and the author are considering different periods, e.g.

A. what % of all videos generated the majority of overall watch time over the last week?

B. what % of all videos generated the majority of overall watch time over the last year?

If the watch time is growing by a high percentage month-over-month, perhaps the numbers would be similar. But, if overall watch time is flat, then you'd expect A to be much lower than B.
Ah thanks for clearing that up for me. But comparing all the Babe Ruth cards to Bitcoin makes even less sense.

2,100 trillion satoshis is qualitatively different than something with only tens, hundreds or thousands of units.

Not to mention that every Babe Ruth card is still judged individually on its relative value to other Babe Ruth cards. Differentiated by its condition for instance.

I just don't see that comparison making any sense.
This amounts to saying that we should accept codebases continuing to contain exploitable vulnerabilities indefinitely. Perhaps for codebases that have a finite expiry date that's tolerable, but for a codebase that's expected to be maintained indefinitely I don't see how it can possibly be worthwhile - a rewrite will be a one-time cost, whereas exploitation is an ongoing cost that will surely exceed the one-time cost eventually.
Can’t we use an icosahedron for a better sphere?
big difference between using the name Signal and writing a third party client.
Long-term COVID-19 effects can include hair loss and heart damage
We do exchange value. Real value. I would not read webpages if I did not get value. Webpages would not be offered if those making them did not get value. Even when there was no commercialism on the Internet at all. Or why people do a lot of things without any money involved. Basing everything on "money" is a scourge. Not to mention the height of inefficiency. Our brains have to deal with something very different instead of the thing itself. Which also lead to a general inability to think about actual things - just "spend more money" to solve something, why even think about the actual things? Money-magic thinking.
> And no, I don’t think it’s unreasonable to believe that I would have access to the movies forever.

Agree. However. I should be able to play the files I have downloaded no matter my account status.

I’m not sure if that’s the case with apple downloads (though it’s my primary method of buying music, and I do suspect it is the case. )
Change windows 10 x64 for better performance in VM or old computers
Interestingly, seeing this made me Google Tamagotchi, thinking my daughter might like an old school Tamagotchi. Apparently, a new “Tamagotchi Pix”[0] product is releasing July 1st. It’s $60 and has a camera for some reason.

Was the original Tamagotchi only marketed towards girls? It looks like the new one will be available only in purple and pink.

[0] https://tamagotchi.com/product/tamagotchi-pix/
Checkout https://GetPorter.Dev it’s basically Docker on Kubernetes.
> And I mean, you could use this logic for everything else. Iterators, arrays, etc. should all have bounds checking too, right? If you want that, there's C#...

I mean yes, the logical conclusion is that trying to backport safety onto C++ is impossible and moving to another language is the only reasonable option. That's kind of the point of the article.
> it would be nice if you could get an assert in operator*

If, as you wrote, operator* for an optional that doesn’t contain a value is UB, it can do whatever it wants, including assert.

I think the problem is that there’s an implicit requirement that operator* optionals that do contain a value is as fast as a pointer dereference.

(Aside: reading https://en.cppreference.com/w/cpp/utility/optional, I wonder how one can misuse “When an object of type optional<T> is contextually converted to bool, the conversion returns true if the object contains a value and false if it does not contain a value.” to write obfuscated code or hide back doors using optional<bool>)
You both made some great points
> three issues: "How big is it", "Who owns it", and "Who locks it"

The issue with this kind of thinking is the belief that there is a "it", not "they".

Say, you are writing a HTTP server [1]. A beginner mindset (what seems to be demonstrated in this post) with start allocating left and right, for every HTTP header, for every piece of string, for every piece of metadata record, etc. Thus, "how big is it" become no bigger than it needs to be. The lifetime of these allocations and deallocations will be made as "narrow" as possible, meaning that the programmer will try to deallocate as soon the they stop needing the data stored; "who owns it" becomes the user of the data itself. And so on.

However, think of an alternative strategy, something which game and embedded developers have been using for decades. You allocate a memory arena when the HTTP request comes. From that point on, every "allocation" is equivalent to bumping a pointer in that arena. If the arena gets full, we allocate another and chain it to the previous one, as a linked list. No deallocations are performed (or could possible be performed) until the Request is parsed, relevant processing is done, and Response is constructed and sent. At this point, the entire arena chain associated with that particular request-response cycle is deallocated in one go.

How big is it? We don't care, smaller than the arena.

Who owns it? That particular request-response cycle.

Who locks it? No one, if different request-response are parallelised wrt each other; otherwise, depends on the nature of concurrency/parallelism.

[1] Usually, I would have given a gamedev example, and then people would have said that it only works in gamedev. That's why I have tried to give a webdev example, considering the majority demographic on this website.

Some reference:

1. Mike Acton's CPPCon Talk: https://m.youtube.com/watch?v=rX0ItVEVjHc

2. Rant by Casey Muratori (Brusqueness Allergy Warning): https://www.youtube.com/watch?v=f4ioc8-lDc0&t=4407s
Do you have a link to the matrix bridge? Do you use signald or signal-go.
Not everyone uses qwerty (or the same layout in general), so complaining about how hard it is to type a certain string of letters doesn't seem like the job of an individual program to fix. It is a very rare and interesting complaint, however.

By the way, is your issue with the t? I think c and l should actually not be too bad to hit, even on qwerty. They're not in the middle two columns, and they don't use your pinkies.

With Workman, c is moved over one to the right, t is where f is in qwerty, and l is where m is in qwerty. So, t doesn't need me to stretch, and all of them become keys pressed with my index fingers, but since you may not like where qwerty c is already, I wonder if this would even be an improvement to you. It does put c and t much closer together, but both are still pressed with the left hand, and then l with the right. Not sure if hand alternation is part of what you had in mind.
Remember, if you work for FB/Instagram, you are part of the problem.
That's a separate question (but equally worth addressing). The point here, though, is that copyright is an explicit bargain with the public domain, and DRM makes it a one-sided one.
As % of global GDP would be an interesting metric.
Is there an antidote to 'digital intensity'?
> Webpages would not be offered if those making them did not get value.

If you’re not paying, you’re the product. Ads are a bigger scourge than “basing everything on money” which is just value made fungible.
Presumably that's why the "JavaScript for" prefix precedes it?
So consulting companies can make bank teaching you how.

After convincing the CIO that 'GREEK' is the silver bullet to their problems.

/s
Never assume malice when simple incompetence is likely.

I have read—somewhere I can’t remember—horror stories of how badly run the corporate owned McDonalds are vs the franchise owned locations. Simple procedures like cleaning out the soda machines on a regular basis are never completed or even known that they should be completed by staff or management leading to mold build up.

In a corporation as successful and large as McDonalds changing anything even if it is seemingly a logical and good idea is more dangerous than doing absolutely nothing. Being a friendly and agreeable employee will be better for career growth than being a hard-driving and demanding employee.

Being the employee that advocates changing vendors away from a long-time proven vendor is a great way to annoy and create headaches for your boss.
The game _Before Your Eyes_ sounds particularly interesting. Not because it takes a hand drawn aesthetic, however that is defined, but because it is controlled by blinks, an action that is only partially under our control, like breathing. This probably won't mean much to people who haven't read about the ways we can blur the lines between our conscious and subconscious minds, but this seems like a way to unlock conscious control over things from heart rate to body temperature to the immune system.