skysight-inc/HackerNews huggingface dataset:
Tesla made 438 millions profit, 100 million are from bitcoin.
If we ignore the profit from carbon credits (they made more from credits than from bitcoin)
they made 4x100 millions profit from cars by your math.
So combined they made more profit than they did.
What comes next? Are they building the perpetual motion machine?
It is pretty funny how things are described when lawyers get involved.

Apple is trying to deflect all the edge cases that show the "stores within a store" they allowed.
Scale of production has never been the problem, achieving escape velocity is.

We need to invent fuels that weigh less to have any hope of getting enough stuff into space to undertake any seriously large achievements.
"I see a great future for very systematic and very modest programming languages."

He was right; there was a great future for that (and everything else in computing). But perhaps he didn't anticipate the FAR greater corporate appetite for functionality. The next feature is paramount. Who will code this next feature? The only path was richer and more powerful languages.
I can. My point is that I can do it without having been explicitly taught touch typing. It's just a skill I developed over time and I thought that it happened for everyone else too.
> Geopolitically this makes a lot of sense.

Geopolitically it makes no sense.

What exactly do they expect any much changing from thus move other than Samsung getting even more desperate, and Korea possibly moving closer to China if the next Korean president will be a gullible populist (which is now a close probability.)

A lion share of high tech manufacturing happens in Taiwan-SK-Japan triangle, all within walking distance from China, and reachable by their nuclear weapons.

The whole of semiconductor industry is %60-%70 Taiwanese play with leading fab suppliers manufacturers often being single vendor, and in Taiwan.

If something happens to Taiwan, the entire semi supply chain globally stops, as happens every time after a major earthquake there.
Well, yeah, their technology would be mostly adapted for their home planet, Earth could be very harsh.
How did the worst colleague teach you that? Did they do the opposite of that?
> n my personal opinion, always optimise for user experience

If you have unlimited money, that is. If you don't, a suboptimal UX is better than no UX.

> Shared code should be in the backend, not in your mobile app. Your mobile app (ignoring camera filters & games, as they should use an engine; unity etc) should just be a JSON viewer, with a small bit of data entry. Anything else is over-engineering, generally.

Ideally, yes, but depending on the app the frontend can still be heavy - e.g. with Coinbase, all the graphing and real-time stuff, done 3 times over, are probably a not insignificant effort.
China will do everything it can to keep the factories in a war, it’s likely the US would offer a lot of Taiwanese US visas especially those in tech, it’s likely the Taiwanese people will have a general strike and the whole place will be very unpleasant to live in after probably many hundreds of thousands of Chinese dead due to choke points getting onto the island. It’s likely after an invasion most production for the West will have to move to other cheaper countries. I can’t see how we can do business with a country that invaded a democratic country.

I really don’t get why China care so much or the CCP see their hold over China as so weak they don’t want to be a part of the world system. But it’s their loss and America will have a clear competitor to focus minds and have a Cold War with again.
> It’s also obsoleted by RFC 8878, to which the same caveats apply.

Tangent: I decided to sit down and read that RFC yesterday. So I downloaded the PDF to my e-reader (because it doesn't support mono fonts for the plain text option). Turns out my Kobo H20 for some reason can't render the "fi" and "ff" ligatures, which made it a real struggle to read at times ("compressed les", "Human Encoding Trees").

Does anyone have any advice for how to turn plaintext RFCs into minimal PDFs with an embedded mono font?

https://www.rfc-editor.org/info/rfc8878
Except Nintendo's strength and main selling ponit was never their hardware, but their vast entertainment IP roster(Super Mario, etc.) which they go to great lengths to enforce its protection. So it's not a good comparison to products who's performance is dependent on being on the latest tech nodes.
Experience Developer doesn't quite have that ring to it... for a resume.
I think developers on call is unusual. You probably got what we used to call “pager duty” because you’re junior. I can’t imagine a company putting senior developers on call. Most companies hide their staff behind call centers and ticketing systems.

The good thing about dealing directly with customers is learning how the product you work on gets used. There’s often a big disconnect between how developers and managers imagine people user the product and what actually happens. Plenty to learn from that.
That is such a bullshit meme that needs to die.

HR's exact goals vary between companies, but unless the company culture is toxic all the way to the top, part of their job is usually to reduce staff turnover (which is very expensive for the company), and in pretty much any company their job is to protect the company against lawsuits. Abusive managers are not well liked by HR.
There's a lot that goes on in a mobile app, please read https://developer.android.com/docs/ and https://developer.apple.com/documentation

It certainly is different to backend development, but not everything is a "JSON viewer", even if you exclude camera filters and games. Only the truly awful apps are "JSON viewers". There is a lot of complexity, and I've heard arguments from people that 'they don't want to be a front-end dev because that is just visual stuff': they're talking about pre-javascript days or talking about something they've never done to a good level.

Using a backend (adding network cost)/ sharing code should be the last on your mind for mobile apps. I've had once, where the logic for feature would take less than a day to implement (which I subsequently did), but inexperienced non-mobile developers decided it would be a good idea (and said exactly what you said) to put everything in the backend to share code between iOS and Android. The interface cost (network code) cost more time in development, and made a much worse user experience. Not to mention, I had to use the code written by the inexperienced person, which had bugs.

You might not understand mobile, but there's a lot more that goes on in a mobile app.
I believe an airship would have higher chances of survival. If the surface has been that hot for thousands/millions of years, why would the underground be different? Unless you go really deep (hundreds of KM?), which is impossible.
It looks like it's not the case, at least looking at: https://germantechjobs.de/jobs/Scala/all or https://swissdevjobs.ch/jobs/Scala/all
So get to live another 40 years but it’s just working longer?
There's a Mercury Flyby in October of this year!

https://solarsystem.nasa.gov/missions/bepicolombo/in-depth/
When the Voyager missions were launched most of the world didn't have international calling. So making a call from lets say Somalia to the US, involved finding a post office with the only international line in town and "booking" a call. Which meant you had to walk over and write down your name (and if you were lucky enough to have a local landline your 4 digit phone number) in a ledger and then walk back home to sit by the phone, for two days to a week, before the operator would call up to tell you the line was available. If the exchange wasn't sophisticated enough to forward the call, you then had to drop everything you were doing and walk back to the post office to use the line. Now think about how anything worked with that level of latency :)
I will never forget the hours I lost debugging an issue where I had not realised that if you declare any variable in scope that coincidentally has the same name as an implicit that you're relying on, the implicit will be shadowed and unable to resolve. Of course, it 'makes sense' when you consider that you would be unable to refer to it by name explicitly... But if you're not using the name, the fact that it can have an impact on visibility is pretty confusing
You are inadvertently trivializing the consequences.

If someone has to pay a bit more for insurance or whatever, that may not sound like a big deal and also morally justifiable if you assume someone is always willing and able to evaluate risk accurately.

However, some diagnoses are treated as "unknown unknowns" rather than quantifiable risks. In that case, it's likely that there will simply be nobody to accept them at all.

The discrepancy between this treatment of a risk as effectively infinite, because nobody will take it on, versus the fact that it is really finite, constitutes economic destruction that would be caused by the disclosure of the diagnosis.

Right now there are restricted circumstances where things have to be disclosed. But it's relatively tolerable because it's limited. For instance, you might not be able to get life insurance, but at least you can hold a job, have health insurance, live where you like, etc.

Taking all that away from millions of people seems not a lot kinder than just liquidating them.
If it is anything like other Chinese goods, i doubt it will even last 90 days. Lol. But I'm sure the Amazon listing for the probe would have 100k positive reviews, even though they probably only made a couple of these.
No need for the attitude, especially since it is plain wrong because Google do judge. Just not as extremely as Apple.
If it was that simple loads of companies would be smashing out 5nm chips...
Valve doesn't even fix VAC bypasses you can find on github
This feels so wrong (and the fact that Google has been doing it for some time makes it feel even more wrong): this kind of address doesn't show explicitly which service is targeted, so it's a great target for phishing and completely fails all the prevention we have been doing. Also, the domain could change hands and provide a different service. Finally, it makes it look like it's a "service" (people will ask, is it provided by the browser?) but it's actually just a marketing trick, because someone paid some money to have it.

Instead of making the internet a better place, this makes it an even more awkward place for us tech and an even more dangerous place for every normal user.
These days it's all about personalised, targeted rolling. You have to find out what song your friend hates the most (say, "Africa" by Toto) and try to trick them into listening to ever-more-horrible cover versions of it.

At least, that seems to be the thing in my friend group.
But wasn't vi the Fancy Tool then?
There’s a difference between obviously absurd ideas and those that someone can go off and try in their own codebase. Giving some breathing room so people can experiment and try things on their own without disrupting the product is being supportive, in my opinion. It doesn’t mean everything should go in. But I give the person the opportunity to sell their idea. Maybe it’s better than I think, or maybe others on the team will support the idea. Unless you’re the only competent person on the team, if the team thinks its a good idea then why not? If you’re the only competent person on the team however, you should really leave the company.

It’s the same thing with code reviews. I make a distinction between issues of opinion vs issues of correctness. I will never let incorrect code get checked in, but if it’s a matter of opinion, then I’m more lenient to let things in.
So you feel for the 'home keys' instincitvely without looking? every time you type? and never had a single lesson?
You mean like a subscription or selling in-app add-ons? Apple take 30% of that too. Trying to circumvent it by pointing to an outsider payment service is a banable offence. In the Epic games Vs. Apple mails have been shown that shows they even talked about banning Netflix because they let you pay on netflix.com. Someone smaller than Netflix would have been removed from the AppStore.
I am glad this came up. I had just started work on synchronizing my Emacs org-mode clock tasks with tree style tabs and i see there are some other good things to check out in this thread. Also signed up for Skeema waiting list.
Of course not. I doubt it ever will. I'm referring to the seemingly common sentiment that working in an office is objectively worse and should be abolished. I just wanted to add some nuance to that.
> It suffers from the same lack of real censorship resistance as IPFS, on which it is based.

I guess, then I2P should be the solution?
ApolloOS is optimized to run on "680x0" hardware, including the FPGA based Vampire accelerators (and presumably the standalone Amiga replacement). So while it will run on original Amiga hardware, it also has optimisations that are Vampire specific (extra instructions etc.)
With all due respect, I think you're blowing that comment on the skewed power dynamic of the U.K. with the E.U., public miss-information campaigns, and inappropriate policies of political leadership, vastly out of proportion.
This has nothing to do with nationalism, but with a sombre sadness about the unnecessary damage caused by brexit.
Liveoverflow ist pretty good
https://m.youtube.com/channel/UClcE-kVhqyiHCcjYwcpfj9w
As far as I know formal verification doesn’t necessarily give way for much parallelism, and the halting problem will not become obsolete, and the latter is a lower bound on many interesting properties.

So unless there is a radically new way to serial computations, that is orders of magnitude faster, I doubt much would change. CPUs are already quite at the limit with super-scalar architectures.
For some reason, plenty of people in management don't seem to realize that raking people over the coals over individual data-points just incentives your workers to avoid giving up data.
> If something happens to Taiwan, the entire semi supply chain globally stops

Sounds like you're arguing in favour?

Also, Koreans will prefer ties with Japan, Taiwan, USA, over China. I'm pretty sure.
You're mixing up two different issues. One is a bug in the implementation of Ethereum, the other is a bug in a smart contract (that runs on Ethereum).

Undoing the former by rolling back the chain and fixing the bug is the only logical thing to do. Bitcoin devs have done the same a couple of times (e.g. [1]).

The DAO hack, however, was not caused by a bug in Ethereum. It was caused by a bug in the code of a smart contract. Ethereum executed this smart contract faithfully (there was no bug in Ethereum). Bitcoin has never done this.

[1] https://en.bitcoin.it/wiki/Value_overflow_incident
what do you mean with 'says enough'?
Treadmills are not a good experience, having only ever run outside for years, I was stuck in a hotel for a week and wanted to run, so treadmill it was. Comparing the two things I can’t understand why anyone uses a treadmill (maybe if outside weather is too extreme?), it’s all the bad things about running and none of the good.

For me running it is about a basic simple thing (legs, feet, shoes one in front of the other.. not much gear) that you can scale up (speed, elevation etc) or scale down (speed, intervals/rests etc) to suit your mood. You are outside experiencing the world for better or worse (sometimes it’s cold/rains outside).

I wouldn’t run on a treadmill either it’s a terrible experience, bad for your running form too.
Contacting her after she blocked him was harassment irrespective of anything she said.

Strongly worded puts it mildly. It was strikingly nasty. Like his literary persona. Good luck convincing a jury they're 2 different people.
Russians landed 10 probes successfully and took pictures and did the science.
Venera 13 lander survived for 127 minutes.

You can shield the probes from sulfuric acid and pressure, but it's hard to keep electronics cool for longer than few hours. Mean surface temperature is 464 °C. (867 °F). Doing science experiments is even harder.
But first, please, citation on how this "statutory or case law" could apply in the first place. It has no more jurisdiction over the kind of people described than the constitution. (Neither, of course, does the original claim that they violated US law.)

This American habit of claiming global hegemony for American law is, on the whole, about equally fucking annoying whichever side it comes from: Yank law enforcement blithely assuming a right to arrest someone who's never set foot in America isn't really all that much worse than Yank liberals who leap to the conclusion that the only defense such victims have is the Holy Constitution.
Maybe this is different here in Europe, but HR's role is to protect the company. HR in my experience does not do whatever a manager wants. Let's say you have a toxic direct, unless you have a 50 page document outlining every single transgression or bad behavior and the steps you took to mediate said behaviour, including corrective feedback, and statements by the toxic employee's peers supporting your observations, HR will often times do exactly nothing and happily ignore you, and even then, they could still propose "mediation" or "conflict resolution" procedures because they are afraid of an unfair dismissal law suit or whatever.
Worst: all it takes is one team member who is focused on finding problems rather than solutions to basically halt team progress
> Have you considered there might be a different explanation here than me lacking "substance" and you somehow being full of it? Ironically, have you considered you might be the one instantly jumping to a conclusion about me just based on a couple offhand internet comments on a discussion that's barely even started?

Firstly, I wasn't saying anything about you but the language you are using.

Secondly, I didn't accuse you of lacking substance, I wrote that your argument lacked evidence.

Lastly, your reaction is over the top, which is also quite a tribalistic response to being challenged.

Yes, now I'm making an insinuation, but that's your own fault for your own faulty assumptions. If you want, we can dial down the temperature and discuss things at a better level, or we can just leave it, not that I believe there's much to discuss other than why you're jumping to so many assumptions about the people you disagree with (or who disagree with you) and their bad intentions.
I'm confused by people that don't see the point in increasing the time efficiency of Python code, citing other languages being available. Python's strength has always been ease of development, with writing performant extensions being much more complex. Projects like numpy have brought much of that performance to easy reach of pure python programmers, but increasing the baseline performance is orthogonal to that.

There's a huge amount of pure python code out there, powering websites, acting as the glue between C functions and providing business logic to pre-optimised frameworks. These are not likely to be targets for rewriting in another language, but that doesn't mean that their maintainers wouldn't like them to be faster and cost less to run.
Thanks a lot for your comment. There's a lot in there. In fact, I added most of it to my personal collection of quotes.
I've never had lessons, I have no concept of home keys (just had to look up what they are), I type everything without ever looking at my keyboard at a reasonable speed.
TikTok and twitch are not same content-wise. It's to feed your content to people if it's just a few seconds. The platform depends on feeding a huge number of very fast changing content to the viewers. That makes it also very simple to analyze the reception of your content.

That's something impossible on a slow paced medium like live-streaming. But the other side us that it's very hard to make real money with TikTok, because all the juicy sellouts that work on long videos and live-streaming, don't transist very well to short clips and a platform with low attention.

Because of that follower-count on tiktok has not the same worth as on other platforms. 1000 Tiktok-follower is like 1 twitch or youtube-follower. People are just getting elluded by the high numbers.
That sounds like you paint corporate control over politicians in positive light.
I am glad that American mogul don't have direct line (preferential treatment) to EU top level officials.
For those who find this topic interesting, there is a walkthrough of the Quake source code by Fabien Sanglare here.

https://fabiensanglard.net/quake3/index.php

He has also written a number of Game Engine Black Books on other games such as Doom.

For the graphics side of things there is a PDF by Michael Abrash that also covers Quake.

https://www.gamedev.net/tutorials/_/technical/graphics-progr...
The harshest part for any machine on Mars is the lack of nearby humans to aid or repair it.
The fuel cost means that almost all of us are destined to spend our lives here on earth. Only a handful will have the privilege of going up in a rocket.
I just couldn't resist.

https://aaa.aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa...
> Lightweight (teddit frontpage: ~30 HTTP requests with ~270 KB of data downloaded vs. Reddit frontpage: ~190 requests with ~24 MB)

Yeah, teddit.net does seem to be pretty light on mobile gas.
We have been bitten by the same behavior. I gave a talk with a friend about this exact topic (diagnosing GIN pending list updates) at PGCon 2019 in Ottawa[1][2].

What you need to know is that the pending list will be merged with the main b-tree during several operations. Only one of them is so extremely critical for your insert performance - that is during actual insert. Both vacuum and autovacuum (including autovacuum analyze but not direct analyze) will merge the pending list. So frequent autovacuums are the first thing you should tune. Merging on insert happens when you exceed the gin_pending_list_limit. In all cases it is also interesting to know which memory parameter is used to rebuild the index as that inpacts how long it will take: work_mem (when triggered on insert), autovacuum_work_mem (when triggered during autovauum) and maintainance_work_mem (triggered by a call to gin_clean_pending_list()) define how much memory can be used for the rebuild.

What you can do is:

- tune the size of the pending list (like you did)

- make sure vacuum runs frequently

- if you have a bulk insert heavy workload (eg. nightly imports), drop the index and create it after inserting rows (not always makes sense business wise, depends on your app)

- disable fastupdate, you pay a higher cost per insert but remove the fluctuation when the merge needs to happen

The first thing was done in the article. However I believe the author still relies on the list being merged on insert. If vacuums were tuned aggressively along with the limit (vacuums can be tuned per table). Then the list would be merged out of bound of ongoing inserts.

I also had the pleasure of speaking with one main authors of GIN indexes (Oleg Bartunov) during the mentioned PGCon. He gave probably the best solution and informed me to "just use RUM indexes". RUM[3] indexes are like GIN indexes, without the pending list and with faster ranking, faster phrase searches and faster timestamp based ordering. It is however out of the main PostgreSQL release so it might be hard to get it running if you don't control the extensions that are loaded to your Postgres instance.

[1] - video https://www.youtube.com/watch?v=Brt41xnMZqo&t=1s

[2] - slides https://www.pgcon.org/2019/schedule/attachments/541_Let's%20...

[3] - https://github.com/postgrespro/rum
If you're happy to ignore that initial part of entering the fuzzy search, "fuzzy search" or "fuzzy find" would have instantly registered in my mind those same examples you brought up. Maybe a qualifier, "on demand" or "by hotkey"?
That ship has long sailed. All the major anti cheat systems do this now, and have done for years.