skysight-inc/HackerNews huggingface dataset:
even if his coding standard allows GL_MAX_TEXTURE_SIZE, I still don't see the point. One (original) GL_MAX_TEXTURE_SIZE is a global constant and his limits.GL_MAX_TEXTURE_SIZE is just a member. You will still need a "conversion" code for every constant there is.

Notice all this busy work

And the code that comes after that is same amount of work, except typing mMaxTextureSize instead of copy pasting GL_MAX_TEXTURE_SIZE perhaps. Is he really complaining about this?

Also is author pushing for everyone should follow one standard? Hard to say what he is asking for.
This doesn’t bode well for Rust in Linux!
> What if someone was laying bricks for 9 hours and then came home ate dinner and then laid bricks for 3 more hours and did this for years and then took a vacation and laid bricks during the vacation as well?

Well, then I would surmise that they must really enjoy laying bricks. And if that's the case, then more power to them :)

> I mean, do we understand that we get a single shot at life.

I'm pretty sure we do. And some of us are lucky enough that we get to choose how we spend it :)
We live in an age where psychopaths and sadists are actively enabling narcissists.
One thing has not improved one iota in the 30 years I've had a cell phone - the voice quality.
Same with paperMC or spigotMC. Get the jar, install java, prepare a custom user.

I do run it inside of tmux, no autostart, but you can easily interact with the MC-console.

---

For minecraft classic on OpenBSD look up Classicube (native C) and MCGalaxie (runs with mono).
> This is especially true in math and physics. You will find that no matter what problem you can think of, either it has already been solved to the highest level of abstraction, or it's an unsolved and famous problem, or not worthwhile/trivial.

I did not experience this in my 8 years in academic math (PhD + postdoc). Maybe it differs a lot from field to field, but mine was positively teeming with unsolved problems. More importantly, it's teeming with paths that will clearly lead to more unsolved problems (of all difficulty and importance levels).

In fact, the thing I miss the most from academia is probably helping new students blaze some of those new paths. Both for their sake, and as a way for me to discover new problems for myself.
Test Environments and Test Data in big enterprises. Scaling from small to huge is as challenging as building the product itself. Spinning new environment on the fly that includes 100's of subsystems, creating an anonymized subset copy of production on demand or generating enough synthetic data on the fly are huge challenges even though some of the tooling exists.

A related problem related to data creation and subsetting is that one person (and practically nobody) knows the entire data relationships between subsystems, but you still need them to create your data.
Awesome, that's a very interesting project! Thanks for the link :)
I’ve prepared my entire life for the “what are your weaknesses” question but never received it in an actual interview.
Thx Rust, but I'll go with Zig lang.
Only by storing it somewhere. So long as it is only passed down a call chain, no problem.

string_view really is no different from a naked pointer. Modern C++ treats naked pointers with well-deserved suspicion. I never have any trouble because pointers are always strictly evanescent values.
Not a Visual C++ user I imagine, because that is exactly what enabling _ITERATOR_DEBUG_LEVEL does.
I've been leraning rust with a pet project of mine (an Apple2 emulator). That was a bit too complex for a start as I had threads and a bit of architecture to structure my code correctly. But in the end, I know understand how rust does threads and memory allocation and I'm now much less intimated by the type system. I still don't get the lifetimes.

Moreover, a lot of the libraries in rust needs you to understand the type system thoroughly sometimes to use them, and some of them use the typesystem to enforce some specific behavior (without telling you :-)). For example, the logger mechanism in rust makes it very hard to dynamically change the logger implementation at run time but it doesn't explain why (in the end, I think it has to do with thread safety, but I'm not sure).

It took me about the equivalent of 30 full days to get there. Although I'm an experienced programmer (C++,assembly,Java,python,R), the last 15 years have been python 99%. Had I continued with C++ all those years, I'm sure I'd understand rust much better.

So, just keep going and really listen to the borrow checker. The thing is really smart and sometimes, after a lot of pain, you understand that your own mental model was wrong :-)
Ocaml is just a mess. Has like two standard libs. You'll just fighting everything but your application logic instead.
Yes, but if you don't do it immediately you won't remember that 12345 means this or that company; and also yes, you can search for 12345 and see that all email coming to that address is from a certain company, but maybe they haven't yet sent any email, etc.

Also if you use random strings that are not actually random (you just try to come up with something on the spot) you're very likely to reuse patterns for different third parties.

In the end it's more "stateless" to have a simple rule to attach an email to a given company, than maintaining a separate reference list (or lists! one in a password manager, the other in your email client).

But it's not very important, and mostly a question of personal preferences.
I've always been confused by the difference between CoreOS and IoT. They're both immutable, based on rpm-ostree but they ship with a slightly different set of packages. I have a low spec VPS, a Raspberry Pi has more RAM than that, I still don't know which of the two editions is best suited for it.

--

I'm very interested in the immutable system idea, I'd like my VPS to run kubernetes through k0s on an immutable base, and I'm considering nuking my Fedora workstation setup and moving to Silverblue.

I've already set up my dev environment to run Emacs in an Arch Linux toolbox (with distrobox). IMHO that's the best Linux has to offer: a stable Fedora host, with the simplicity and breadth of packages of Arch Linux to develop in.
I just need a way of filtering out idiotic content produced by people with limited cognitive abilities and professional trolls and provocateurs.
"Some binary" = the same version of VS Code (maybe without Electron and some other parts).

Makes sense as you need to - edit files, run tasks and terminals, and run extensions which access the remote filesystem (eg Jump To Definition taking you to header files installed in system folders) - basically everything you need VS Code to do when you run it locally.

The alternative would be running VS Code as a webserver remotely and the local VS Code Electron just acting like a browser window pointing at your server. It probably wouldn't feel as responsive.
I think he is complaining about not being able to copy paste GL_MAX_TEXTURE_SIZE to limits.GL_MAX_TEXTURE_SIZE? Otherwise I am failing to see the point as well
I don't think I've ever heard anyone refer to a software package as "a code."

Then you probably haven't been around physicists, or read enough physics-related material. A non-scholarly reference which can't be easily checked online is George Dyson's "Project Orion," where Freeman Dyson (author's father) is quoted as mentioning this or that "code" as significant for the design of various Orion parts. (That should be a native enough English speaker.) The time-frame is late 1950s to early 1960s.
I disable voicemail. Hate it.

It's an avenue for abuse that's can't be triaged at a glance, as you've found.

People can SMS me. Then I can block numbers from abusers.

(no comparison intended to perpetrators of emotional or physical abuse)
Great question. It will be any upper caste who are above Dalits. There is no one perpetrator here but all of them. The main point to note is that the caste hierarchy is sacred and will be enforced by endogamy (arranged marriages) and other occupational rules.

You will be shown your place very very quickly. Love marriages are quite deadly and parents killing their own children and the lower caste grooms are extremely common. You can search for "honour killings in India".

Please read "Annihilation of Caste" by Dr. B.R. Ambedkar. Its around 50 pages of an undelivered speech, later published.

If you want to learn about caste, please make sure not to ask for explanations from an upper caste person. This is extremely important!!

Example of this enforcement: https://www.bbc.com/news/world-asia-india-15997648
Western languages invented all that fancy computer stuff. Maybe we should keep them.
I don’t think it’s true that any given “basic” design pattern should should necessarily be simple in every language.

Certain things are short and elegant in Rust. Certain things are short and elegant in Python. Each optimises for different things.

I also don’t believe it places “extraordinary complexity” on the shoulders of the programmer; this complexity is often a sign you’re doing something wrong, or working against the grain of what Rust is optimised for.
Ok, well it seems like you have a clear plan.

Just a heads up, the battlestar code is pretty large, so you might want to code / use as an example a simpler game and then if anyone asks if it can be used for more substantive games, point to the updated and working version of the battlestar code.

That way people can see:

- You have a working thing

- There's a nice entry point tutorial

- They have some example code to look at of more complex example for when they have to build something larger, which is super useful besides reference documentation that people rarely provide.

In fact lots of small examples of things are probably going to be useful for you, as lots of people you're going to be engaging with are going to want to copy / paste stuff.

Lots of luck and please post a Show HN when you're next releasing something!
> The important difference is in purpose, not implementation.

I couldn't disagree stronger on that one.
Abstraction is generally good, but this becomes a purely philosophical discussion as soon as you ignore the actual implementation when talking about the differences of how something actuals behaves and should be used. And philosophical discussions like that have their place but are imo pointless in the context of what should be used, when. They're generally better placed in a context of deciding wherever you want to implement an abstraction

I do fundamentally agree with the rest of your comment however.
that's what I meant with trusting your language to prioritize workloads vs your OS.
If we programmed in Chinese, one would need to know thousands of characters to write any decent-sized program; if we programmed in Japanese, one would need to master several alphabets, if we were to program in Hindi, the very shape of our characters would depend of the context...

All in all, the upper/lower case problem does not seem to be that much of a waste of man-years.
wow. That's deep.

TLDR: Don't get stuck at "0.1x". Do leetcode and switch while you get competitive salary.

In a new company you are usually 1x for the first year. You might be a 10x for a while after the first year then some thing changes like a project move or disagreement with technical decisions/manager/raise then you become 1x and then 0.1x. This is a dangerous time. Better switch. If you don't in the next appraisal cycle you will get compensation below you skill level and then its hard to get your compensation back.
Yeah, but it doesn't help on shared-memory process concurrency, and we all know that in 2022 the best way to ensure secure software is to go back to processes.
this is restricted in physics, e.g., life sciences need as more as they can get money, they even do not have enough money to pay assistant, there are so many species waiting for identifying, even use old protocol, scientists still need to pay salary, specimen storage fees...
Yeah, I'm not saying don't do it. Just, it's good know what you're getting yourself into before you start. There is a tipping point.
What exactly is the reason people started to have upper and lower case letters? I found a few articles about this appearing in the middle ages, but there doesn't seem to be a reason that makes sense. Seems to add nothing to the language, wtf is the point of the first letter being a capital anyway, and rules about various words that have to have caps?
One is development. The other is system ops. Some people like to handle both, and others don't.

I spent the last year migrating our backend off of heroku onto bare metal Proxmox servers with unlimited VMs. It blew my mind that 0, literally 0, of my developers took up my offer to give them free VMs (including KDE/Gnome with NoMachine/NX!!).

It turns out that my devs just want to be devs, and not use their free time to play on sys ops and k8s and ceph clusters.

When I saw this happen, I started hiring staff for sysops separately than expecting my devs to do so, and see much more clarity in output.

In summary, if you're writing the LAMP CRUD app, maybe someone else oughta be the one to deploy the service mesh.
I meant an email for asking questions, etc. But nevermind.
> But consider the WSJ audience and the way cryptocurrency is increasingly being peddled as a legitimate investment.

If this audience doesn't understand what they're investing in and the rules around it, they're not very good investors, are they?
Obviously not. But an enduring large fraction are, and remain. And code there is practically never improved or modernized, only patched onto. It is a cultural thing: there is no perceived value in anything but new bullet-item features.
He meant "charge".
never ask a woman, her age

a man, his salary

microsoft, how much of `$ strings ./code | grep HTML` are references to LGPL Blink class names
The solution to this type of intentionally incompatible product is to return to a legal and cultural environment that respects adversarial interoperability[1]. If a company doesn't want to implement the features people want[2], some other company should be able to provide their own (possibly reverse engineered) implementation.

Trying to restrict competitors from making interoperable products is admitting you don't want to participate in a well-running competitive market and instead deserve monopoly power.

[1] https://www.eff.org/deeplinks/2019/10/adversarial-interopera...

[2] including features like interoperability with a competitor's product.
Well, we are in the comments for an article which exactly disproves your point. You say Indians don't care about caste but I want to see some intercaste Indian couples and Indians without caste surnames among your "first-generation" Indian Americans.
GitHub Codespaces is a paid service and they don't want any competition. Charging for Visual Studio every two years is old hat. Charging companies for their IDE by the developer-hour, now that's Thinking With Cloud.
10x is real. Those programmers are still alive. Example Jeff Dean.
Confluence Zero Day Announced
Exactly. This is extremely petty and particularly among software developers who are keenly aware of this sort of behaviour, a little bit self-defeating.
Sans for Java, for which IntelliJ IDEA still holds a little bit of an edge in terms of syntax highlighting, lots of people are moving to VSCode. Besides all the nice little features (like jumping through code, markdown render, e.t.c) it has 4 big advantages.

First, VSCode remote SSH extension is EXTREMELY useful - any computer you can SSH to you can edit code directly on with any extension.

Secondly, terminal integration is super nice. You can configure keybinds specifically for the terminal (and in general, they are pretty well set up default). So for example if you are using remote SSH extension from windows to linux, the terminal functions just like under native Linux.

Thirdly, for data science dev, native Jupyter support is super nice.

Fourthly, the remote SSH integration also works extremely well with Windows/WSL2, which is arguably the best way to have a "dual boot" system today. You get the widest range of software/games that you can run, with almost no drawbacks in comparison to running native Linux. You can do all your dev in WLS2 nicely with VSCode, just like you would under Linux, including things like docker, CUDA for ML, e.t.c. Even graphical linux apps work now.
Putting an if statement in your loops shall slow down your loops. Instead chunk/partition the loop and run it in chunks.
Amazon’s Kindle bookstore to quit China
Murena launch privacy-centric smartphones: DeGoogled Android phone does the job
As an Italian, I say that the top reason is not schooling or scarce attitude, it's humiliating salaries.

You work hours and hours and get peanuts for your efforts. While your employer buys the 5th Porsche.

I come from one of the richest regions, yet as an IT professional I felt appreciated only when I started working abroad. No matter how much I tried, most job offers in Italy are ridiculous.
Yes, I'm going to start using a fork that exists solely due to personal grudges
> Having a complex programming language which limits you and controls how you use it does not sound appealing to those who need a feature done, fast.

This is so interesting to me. I'm a Rust programmer by trade (as in - I'm not a hobbyist, I actually write Rust for work). We've found that, while the feature work is a bit slower in Rust than in other languages the company used to use (mostly Python), they tend to require a lot less maintenance down the line (less bugs, easier refactoring), and so it ends up canceling out a bit.

I also never find that Rust limits or controls me in my day to day work. There are some things you cannot do easily, sure, but those things tend to not matter in application code. Linked lists are hard, graphs are hard, but when writing an app, I just use an existing dependency like petgraph or std::collections::LinkedList instead of reimplementing those datastructures. And if you need to write those things, it's not like it's impossible, you just need to drop down to unsafe rust, and ideally figure out some safe way to expose that API.

Really, the biggest disadvantage of Rust is that its learning curve makes onboarding newcomers much harder if they don't have experience in the language. For Python/Go/JS/Ruby you don't really have this problem, even if a potential recruit doesn't have experience in the language, they will probably be able to pick it up as they go without too much trouble. But in Rust, it can take a fairly significant amount of time to get up to speed and stop fighting the compiler, in the order of several months.
In a video from few years ago he mentioned "electromechanical prototyping" at Verily ( https://en.wikipedia.org/wiki/Verily ) previously called Google Life Sciences which is doing healthcare and biotechnology related research. Not exactly the first thing you might think when hearing Google.
I think they mean tearing an editor (or other panel) out into another window to move to their other monitor.

Currently you can open another window, but it comes with its own explorer, terminal, problems, test runner, etc. Soon you'll have the same file opened twice in different screens, and... bleh.
How charming. Everybody loves having their language use corrected sarcastically.

But you should really read up on your English modifiers next time, because your point is based on a common vulgar-linguistic misconception. “Linux,” in this case, is plainly being used qualifyingly rather than classifyingly. It’s subsective, but ambiguous as to whether or not it’s intersective - but I think the answer to this is quite clear. Say we had to reformulate the noun phrase into a clause. Would we really come up with e.g. “The `cheat` command is Linux-specific” as the equivalent intended meaning? Or would it more likely be “The `cheat` command works on Linux”? The point is that the `cheat` command can be used in a Linux shell, not what scripting language it’s written in.

> Accuracy is not pedantic

This is the wrong attitude, my dude. Wrong, wrong, wrong. It’s probably intended to be light-hearted because it’s self-referential and self-contradictory (pragmatically, not semantically, as ironic humor does), but it’s still too close for comfort in this context. I know computer dudes who are like this for real. One graybeard almost had me saying fuck this when I was still starting out.

> No. That’s idiotic reasoning.

…
I'm not sure, there's something good from that fresh perspective: why do we have software that's that broken and why do we think this is normal?

We've given up on logical systems and we deal with so much complexity that we're dealing with kind-of-biological systems where reasoning about the system is not possible anymore.
I feel an incredible disconnect with people like this who casually tell public stories about their youthful credit card fraud and other computer crimes (cf. every single story in Hackers: Heroes of the Computer Revolution).

I understand the anti-capitalist (or at least anti-corporate) and anti-authority attitudes of hacker culture but these stories are not told by anarchist cyberpunks "sticking it to the man" but almost invariably by sheltered (usually WASP) yuppies working for billion dollar companies or in this case, Slack.

These aren't so much stories about clever hacks and youthful rebellion but of a youth isolated from consequences for criminal offenses that would otherwise have been sufficient to give them a career-ending criminal record.
>"bias against creativity that is not necessarily overt, and which is activated when people experience a motivation to reduce uncertainty."

Would this imply that inhabitants of countries that rank high on the Hofstede ambiguity tolerance scale might be less biased against creativity :o ?

https://en.m.wikipedia.org/wiki/Hofstede%27s_cultural_dimens...
Really long version. The market finds that this is not a viable business model (at least too vulnerable to economic shocks). I am not unhappy about that, because the alternative scenario where ex criminals who caused harm in one way or other get to be a vulnerable population (marketed that way through this startup) to which companies would give preferential treatment because it looks good to help vulnerable populations, would be a tough pill to swallow for people who have not done anything wrong and will not get a good job as a result. I hope this clears up my point of view.
What FLIR camera is that? I have an E4 and it does the same thing described in the article; inside the crappy jpegs is the "raw" data embedded in them.

The FLIR desktop software uses this data for further analysis and you can export higher quality PNGs from there.
Rust is young, very ambitious, of course general purpose enough to do everything in it, but its ecosystem has serious gaps. (And some of those are dependent on planned language level features.)

...

I spent a lot of time reading r/rust, various blog posts before going beyond helloworld in it.

To me it's in the same category as Scala (ZIO) or TypeScript. Both are very powerful, a joy to work with them, until the low-leven limitations hit in (JVM or JS).

However I don't interpret that as a sign of oh we need to go back to assembly, but more like, okay, we need to accept that our tools and the problems we use them on are not in harmony (yet).
Eh, he receives gadgets from all big players to test, and is very upfront about him returning the stuff after. No one does as thorough reviews about sports gadgets as him. He also publishes all the raw data, so GPS bugs etc. is very visible if they're present, don't feel he hides anything when reviewing Garmin stuff. Sometimes he is even very critical.

If anything, if he were in favor of Garmin he wouldn't push this so hard, since it's in favor of Garmin computers that a competitor can't read this data.