skysight-inc/HackerNews huggingface dataset:
In very broad strokes, changes to the language work like this:

* Anyone may write a proposal

* Anyone may comment an open proposals

* The people on the Rust team decide to accept, reject, or postpone a proposal.

Those people on the team have the power to gate any major decision about the language itself. Some big company could hire 500 Rust developers (let's make it ridiculous on purpose), have them write 1000 proposals for new features, but that doesn't mean that those changes will happen: it requires that team of people to sign off on the decision. That group of people is added to only with the consent of all of the existing members. Additionally, making decisions is a consensus based process, so a single "no" vote will mean the proposal is not accepted.

Now, that doesn't mean the process is immune to companies suggesting things. For example, a company could try and hire literally every member of the team. That would be... aggressive. They can use their resources to give more people more time to do the work of making a great proposal, building consensus, and making changes they want to see happen. That is actually an ideal situation, and has been working pretty well historically. (Google employees were key in getting async/await to work out, for example. This is also basically what Mozilla's influence on Rust was for its entire history of working on things.) This is the way I'd personally love to see Amazon (and others) contribute.
Seems like a plausible real reason would be that he didn't even bother to attend team meetings. Making oneself indispensable among peers is kind of the obvious first step everywhere on the road to getting more equity.
Parent claimed that they got more out of search than google did. Parent did not claim that they got more out of search than google did, divided by the number of google users/ad targets.
AI Trends to Watch in 2021
That was a bug in the smart contract, not ethereum.
Ethereum never had base layer bugs that allowed for infinite inflation, bitcoin had - last time in 2018.
Answering in a short, simple, probabilistic sense: they probably wouldn't comment.

Answering as a more seasoned, cynical person professional sense: that's way too simplified. Processes and standards for police, judges, officials etc, differ all over the world, as do professional ethics and culture. In practice there are various incentives and norms and "professional wiggle room for professional ethics". The police often release images of suspected persons or specific evidence precisely because they want the public to connect the dots and report their suspicions, knowing full well it results in false positive reports (and often withholding additional evidence for release). A doctor might not be allowed to euthanase, but they can prescribe high amounts of pain killers. A prosecuter might not go post on reddit, but they might act through a sock puppet or leak through the media. A defence may do the same. Corporations hire consultants and PR firms to give the illusion of justification and action at a distance. A judge would probably not comment on reddit (if not just because of the professions technical illiteracy), but the conditions of their appointment, their staff, political alignments, social circles, tenure, and professional ethics etc are far from uniform and sterile. All of the above are liable to cognitive, emotional and systematic failings and biases in addition, as well as the failings of their education and background: on a personal anecdote, I find judges and lawyers notoriously bad at reasoning that requires math or probability. In my experience also, those in power frequently strategically leak, work through proxies and associations to avoid the image of going against professional standards and save reputation.

additionally, in adhering to professional ethics, we don't necessarily approach the truth (which is presumably our goal), as following systematic cultures and professional ethics can lead to bias: as I pointed out, these official systems frequently come to the wrong conclusions as well, and going against the norms of professional standards can be used to silence critics, shun whistle blowers, and protect the general institution.

All this comes back to my original point: don't just believe something because it's posted in reddit. But don't discount it as being inherently inferior either.

Be skeptical, but be a skeptic of reddit and officeholders. Think critically. Learn to think and the process of thinking: it's not just natural, it needs to be learned and practiced. Learn the biases and common mistakes. Observe the evidence and the process used to come to the conclusion, and then make a judgement.
And in the cloud native world everything is on the Go track. Java were huge for big enterprise monoliths, but it seems like this is not what we are heading for in the future.
Comma.ai Drive and Office Tour
Alternative article: https://www.itnews.com.au/news/covidsafe-data-incidentally-c...
Perl was great. I miss Perl. v_v
When they were owned by Nokia you knew Nokia wants Qt to be used everywhere. Now it's not safe to use it without a lawyer on retainer.

Plus, from my friends who still do Qt, they're trying to turn it into an Electron-like platfom with Qt Quick and QML and the result isn't exactly the dependable platform that we used to know and love.
I mostly use Go. But I've been keeping an eye on Rust because I like the language expressiveness, the safety provided by the stronger type system, the smoother integration with C calling conventions, the generics, the error handling. But I'm hesitant to switch to it because it feels like the learning curve is steeper in Rust than Go, and that's important for my team where we want to be able to onboard new engineers quickly. What's your experience in that regard?
Reading the Media Guidelines, I don't see how you came to that conclusion:

> TL;DR: Most non-commercial uses of the Rust/Cargo names and logos are allowed and do not require permission; most commercial uses require permission. In either case, the most important rule is that uses of the trademarks cannot appear official or imply any endorsement by the Rust project.

https://www.rust-lang.org/policies/media-guide
Twitter previously invested in Scala, which significantly contributed to it's adoption outside of relatively small community back then. Another part of success was Spark.

It looks like Rust gains bigcorp support, all we need now is a killer product written in it to kick off explosive growth.
Compared to the supply chain for an EV motor, the supply chain for an ICE is incredibly complex and ripe for disruption. When that disruption occurs things are going to get real interesting, real fast.

(As one indicator to watch, Bosch is a German conglomerate that alone makes a surprisingly large fraction of the ICE supply chain and key parts in almost every major ICE from at the very least US and German manufacturers. Bosch has rumored a pivot for several years now that the time for them to get out of ICE vehicle parts is coming up as all the German manufacturers plan to go EV only. If Bosch makes that pivot they would hugely disrupt ICE costs. That's just one conglomerate of a dozen or less capable of that kind of disruption right now.)
I'll use this thread to share one of my oft-wished features: all mobile apps should come with an on/off toggle, too.

Sure, I can delete the app, but if I think I want it in 2 weeks (say, while travelling), there are a lot of activities I might want to disable for some duration, without deleting or losing the local data.
I agree that Java is not going anywhere, but I could absolutely see a world where JavaScript and Python are number one and two.
Here's one that I know of: "A2: Analog Malicious Hardware" (2016)

https://www.researchgate.net/profile/Kaiyuan_Yang5/publicati...

Abstract:

> While the move to smaller transistors has been a boon for performance it has dramatically increased the cost to fabricate chips using those smaller transistors. This forces the vast majority of chip design companies to trust a third party -- often overseas -- to fabricate their design. To guard against shipping chips with errors (intentional or otherwise) chip design companies rely on post-fabrication testing. Unfortunately, this type of testing leaves the door open to malicious modifications since attackers can craft attack triggers requiring a sequence of unlikely events, which will never be encountered by even the most diligent tester. In this paper, we show how a fabrication-time attacker can leverage analog circuits to create a hardware attack that is small (i.e., requires as little as one gate) and stealthy (i.e., requires an unlikely trigger sequence before effecting a chip's functionality). In the open spaces of an already placed and routed design, we construct a circuit that uses capacitors to siphon charge from nearby wires as they transition between digital values. When the capacitors fully charge, they deploy an attack that forces a victim flip-flop to a desired value. We weaponize this attack into a remotely-controllable privilege escalation by attaching the capacitor to a wire controllable and by selecting a victim flip-flop that holds the privilege bit for our processor. We implement this attack in an OR1200 processor and fabricate a chip. Experimental results show that our attacks work, show that our attacks elude activation by a diverse set of benchmarks, and suggest that our attacks evade known defenses.
I posted recently on a large subreddit to promote my app. I read the rules on the side of the page that indicated which day to self-promote and what flair to add, etc. I still got banned a few minutes later, and the post taken down.

I asked the mod why and they directed me to yet another page with a huge list of rules that weren't referenced in the self-promo rules I had seen. I understood the intent and it's their rules, but it did leave a bad taste in my mouth, having tried in good faith to follow their instructions.
I do that occasionally, but it's never to single out an employee. If I'm sending things out that my reports can't or don't want to read, I'm wasting everyone's time.
> Yet caddyserver.com still doesn’t support it.

Right, because Matt (and the large majority of everyone on the internet) doesn't care.

> It’s definitely a red flag something people should know before using caddy, as it’s a sign caddy will also interpret other specs funnily.

Pure FUD. It's such a non-issue. As you've been told many times.
Prepare to be FOIA’d NSA emps.
Claudette Colvin.
That is an interesting approach. Maybe I should do something like that too!
I assume it's the same reason many tube amplifiers expose their tubes... they want to highlight their differentiator and for you to see them for exactly what they are.
I tried this just last week, and I've gotta say, out of all the templates and frameworks out there these were the easiest to use and tweak.

Because it really is just HTML with utility classes, you never end up in a situation where you have, say, a "card class" you can't really override without a bunch of `!important`s.
The face recognition cameras catch you on the way out, the camera catches you on the way back in.
Sorry, that wasn't a dynamic linking dig, but more of a JIT dig.

I agree that rust would be better with dynamic linking. It sucks that you have to build everything when you build one thing :(.

The issue I was specifically thinking of is how slow an untuned JVM can be for startup times and to get to peak performance (It HAS gotten better, but is nowhere near as fast as rust or even python). The default for these JITed languages is to pass everything through a non-optimized code path and only optimize later when the various methods are exercised enough.

Rust has an advantage here in that it doesn't do any sort of runtime analysis to improve performance. It simply is as fast as it always will be.
Just take it out of the <a> element and add a tooltip to it.

The pedants will inspect the source code first before asking.
AHK is better for stuff like this, something like

#Persistent
SetTimer, CapsLock, 60000
return

CapsLock: Send {CapsLock}

AHK is very small, 0 on resources and this script is visible in tray. You could even enable/disable it via another hotkey or when specific app (PDF reader) is started.
I don't think anyone is literally going to starve to death if they are unable to deceptively pimp their own software startup on Reddit.
Net.art
Emailing jeff at amazon.com no longer helps
Having worked extensively in both finance and defense, your assumptions are way off base. This kind of monitoring is the purview of corporations like Amazon, Walmart, McDonald's, and others who treat employees like machines. Defense and finance have highly skilled brain workers and they aren't micromanaging performance metrics like this. They are tracking information access for security reasons where appropriate, and in the case of finance, tracking results insofar as it relates to risk and profit, but they're not monitoring grunt-level input metrics the way you imply.
> the benefits of which might not be particularly relevant on large established projects who have probably addressed that problem a long time ago

It's quite the opposite: the larger a C/C++ project gets, the more problem you are starting to have with safety. Securing and modifying millions of lines of C/C++ code (especially if it's multi-threaded) is a nightmare, and actually impossible, where people are afraid to refactor old code because all the ownership uncertanities.

Rust changes a global ownership tracking problem to a local one.
Want to work with Rust?

Ockam.io loves Rust, and we are hiring!

https://www.ockam.io/team#open-roles
Given the BBC based most of its news of social media...

“It’s obviously Bigfoot, the human/ape hybrid the greys use when on Earth.”, says a source near to the monolith.
Damn that's gross. When I asked my Android Auto for a weather report it gave me the weather and then said something like "by the way, I can read you the news: just say 'hey google, what's the news?'" That annoyed me as well, but at least it wasn't trying to sell me something. I also understand that feature discovery is extremely hard on these voice interfaces, so I'm willing to let the Google thing slide as long as it doesn't do it too often.
Exploiting DeFi Apps with This One Weird Trick
It's fascinating, the diversity of the cultures of the world. In my country a mom cares about her toddler, providing her with food, clothes and being on top of her on almost in a by minute basis. When you are an adult you are expected to perform you work with initiative, personal responsibility and without the need to be micromanaged.You talk with your boss from time to time to communicate and get guidance. It seems in your country is the other way around. Marvels of this big wide world.
There is no coherent "software industry" as a unitary entity with shared norms and standards. There never was.

Since all you really need to get started is a laptop, there are rather millions of more or less atomized software shops and developers attached to other industries, other streams of revenue and capital, other entirely disconnected cultures and social norms.
> I don't want it to be a clusterfuck like IETF and web standards development where companies like Google, Apple, Cloudflare, Mozilla get to dictate what is and isn't allowed on the web.

You may want to note that there's a pretty damn big difference between the two: the rust project needs to be interoperable with itself and that's about the extent of it.

The web needs to be interoperable period, so if there isn't some sort of buy-in or the ability to push your weight around, spec-ing or implementing something is just a waste of time.

Putting resources into the language doesn't mean you control it, and volunteer-driven projects go where they will. Python or Ruby are not owned by their sponsors.
The forgotten Hawaiian Islands in Canada
1. Go on reddit

2. Find places relevant to your product

3. Talk about your product when relevant

magic.gif
Then what's your take on the article I linked?
Why would a person be threatened by a language? I'm asking the HN community why I should reconsider and to share their thoughts on having used Rust.

The world isn't made up of people who either love or are threatened by things. Could you not use this language?
Like the construction with big, classic components with through-hole mounting. A complete klutz could solder this. :)
I tend to refer to asm.js and wasm interchangeably, but yes, wasm would be the technically preferable term.

Never heard of AssemblyScript, but yeah, it or a statically typed language like it is where frontend development needs to go. In concordance with my point about TS being fundamentally unsuitable, the AssemblyScript docs (https://www.assemblyscript.org/basics.html#strictness) say:

> WebAssembly is fundamentally different from JavaScript, ultimately enabling entirely new use cases not only on the web. Consequently, AssemblyScript is much more similar to a static compiler than it is to a JavaScript VM. One can think of it as if TypeScript and C had a somewhat special child.

> Unlike TypeScript, which targets a JavaScript environment with all of its dynamic features, AssemblyScript targets WebAssembly with all of its static guarantees, hence intentionally avoids the dynamicness of JavaScript where it cannot be compiled ahead of time efficiently.
Great news, now hopefully they implement a CSS fallback for older browsers. I can't get their site to load at all in Pale Moon because it's white and unreadable.
Hum… I did validate the idea of my product on Reddit way before it was built.

It really matters on what sub you choose at what stage. Some subs are ok with half baked products, some will trash you!

Just spend some time on your target subs, try to understand what works, what don't and post accordingly!
Hello World Node.js Deployed to AWS Fargate with Auto-Scaling
no im not saying that at all. i said what i said, you drew a simplistic conclusion based on what i said which fit your own narrative: "but I think giving the rest of what Modi does this would be more cynically down by the Indian government than you make it out to be."

not sure what any of that had to do with what i said, i was not trying to make out anything. i was simply stating that something that can be added to this perspective regarding OPs post, is that there are simultaneous forces at play. you do understand that two things can happen at the same time right? one does not negate another?
Are you sure. The EU mandates much MORE monitoring in most cases. Self driving cars may need to have camera's on occupants to monitor them during driving etc. A lot of the safety stuff in EU is MUCH more nanny state and CCTV is much more widespread it seems. Also very power data collection and centralized databases about everyone in the EU (ie, I don't think "states" or localities issue local ID's).
Any model superior to what Jane Street is running is worth vastly more than the prizes they’re offering.

If you prove such a model out, get licensed (SEC, FINRA) and start soliciting to manage assets.

Disclaimer: Not investment advice. Not a lawyer, not your fiduciary.
It was an absurdity at the time.
I remember the same story about go while we had microservice craze. Now it is not a sexy language anymore
now that Bootstrap uses the system font stack, using it doesn't have to scream "I AM USING BOOTSTRAP" any more
I am not a lawyer either, but:

> When you add a license, is the codebase “licensed going forward” or does the code at the revision behind the “added license” commit not have the license applied?

I believe verdverm is right. Unless you make an explicit announcement somehow about previous versions, your licence document would be taken to apply only to the version(s) of the software that bundle that licence document.

> curious what happens if the license is changed

Same principle applies. You could explicitly re-license the old versions of your software under the new licence as well.

> follow up question: licensing per-file vs licensing per codebase

I think you'd be on fairly safe legal ground just including a licence document with your project, but GNU recommend you include a short notice in every file in your project, directing the reader to the full text of the licence. [0]

[0] https://www.gnu.org/licenses/gpl-howto.en.html
> If they really want to help, the most obvious first step would seem to be to formally adopt and throw some full-time resources at the Rusoto AWS library set for Rust.

Is it really? Seems to me like that would easily be seen as self-serving, while putting efforts into the ecosystem as a whole means even people who don't care a whit for AWS benefit.
>I'm wrong and can't have those thoughts.

There is a difference between facts and opinions, yah?
It has C and C++'s performance without a lot of the footguns. A better type system. The trait system is a nicer way to extend types than C++'s class system (IMO). Generics from the start, instead of absent (C) or added on and still not fully utilized by practitioners (C++, some practitioners get the value, other offices bar using them). The ownership model means that using the lower level concurrency primitives is less likely to have the subtle issues of C and C++. It also means they could avoid encoding a specific concurrency model into the language (like Go or Erlang) and let those be libraries.

Cargo as a standard build system, package manager, and test runner. This makes for a much more coherent development environment than the tire fire that is C and C++'s build, test, and package management story.

Developing tests is much easier than in C and C++, which means many of the packages are actually reasonably well tested (maybe not perfect, but better than the average C or C++ package you might want to incorporate into a project).

Rust has a pretty good module system. C has nothing of the sort, and C++ has a mix of things that can be used similarly (classes, namespaces) and only recently got modules proper in C++20. This helps a lot with organizing your code into a modular structure and then sharing that code with other projects.

Rust can call and be called from C, so there is no tossing anything out. You can integrate Rust into an existing project one file at a time. Move your more critical code into it, and let other code call it. Going back to concurrency, put the part that generates and manages workers (as an example of one model) in Rust and leave the rest of the logic in C or C++. Gradually migrate the worker logic into Rust, or not. Perhaps it's a library that you don't control or don't want to change.

Some things aren't pretty or aren't clear. For instance, str and String are pretty confusing for new users. But the compiler will catch these for you. Speaking of, actually decent compiler warnings and errors. Often with potential fixes included, which usually do what you want.

In summary: Fewer footguns, better quality of life components, better language features in some areas (type system, modules, in particular), no performance hit (or no major performance hit) compared to other options for languages attempting to offer improved safety (where safety could be along many dimensions).
I have steered away from Obsidian and the like because they are not native. I tolerate and use many web apps, but the only Electron app I really enjoy using is VSCode, because it's optimized beyond belief and has a specific use case.

I want my notes apps to be native, thanks :)
We were constantly told in school "sarcasm does not communicate well over text!"

Between , , and WrItInG lIkE tHiS, the situation has greatly improved since then.

EDIT: Aparently HN is not displaying the eyeroll, facepalm and upside down smiley emoji.
Rust has a lot of deficiencies, like any programming language, but in general what I've seen is that "the community" believes the ownership model/lifetimes and "unsafe" keyword effectively makes it flawless. I think it's dangerous, to be honest, and the community in this regard is not very good--it's filled with people who hype the power of the language well beyond its limits.