skysight-inc/HackerNews huggingface dataset:
The reason these post-2005 cross-platform envs have gained no traction is because so many devs won't move away from browser - or even consider alts to a browser exist. Suggesting something not SAAS, PAAS etc. right now in most enterprises won't do much for your career.

WASM kind of fixes that - it takes that 90s/00s native speed into the frontend of the moment and makes complex UIs more viable. Any dev with more than 20 years experience shakes their head that it takes WASM to make that happen - but I'm just grateful it is.
I don't see the three languages as very different because Algol 60 is their prototype. The distinction between interpreted, VM, and compiled is an implementation rather than a language distinction...e.g. Jython runs on the JVM; Excelsior Jet compiles Java to native code; and Rusti is a Rust REPL.

https://en.wikipedia.org/wiki/ALGOL_60#Examples_and_portabil...

https://www.excelsiorjet.com/

https://github.com/murarth/rusti
>the reality proves that the commercial web in general can not be trusted with so much power over layout.

That's not a reality, though, that's an opinion. If we were to "dumb down" HTML5/CSS and remove degrees of creative freedom from authors in favor of centralized, client-side solutions, we would do so for everyone, not just the "commercial web."

A web where everything looks and behaves exactly the same is a web which is only interesting to a minority of people. That web would probably have never escaped academia and the world would be worse off for it.
Both are good points. It would probably be more accurate to use life expectancy at 25... so it starts around the time people start their careers, and it excludes all children deaths (who never contributed). If we did that, it's an increase from 71.5 to 80 (more than doubling retirement years, from 6.5 years to 15).

Source is here, starting on page 53, there's a nice table of life expectancy by age and date:
https://www.cdc.gov/nchs/data/nvsr/nvsr65/nvsr65_08.pdf
Well, they could commit suicide and get a Ballmer clone.

They lost control of the client (it's web + Android/iOS now), steering away from the current course and back to the old one is a sure way to irrelevance.
There isn't much reason to give unfinished language (0.6.3 version as of now) lots of exposure, since lack of useful features / libs / docs / etc might be a potential turn off. Usually everyone starts to jump on a hype train prior to 1.0 release.
I couldn't find your e-mail address, so I sent you a tweet.
It really looks like it by the website, but I haven't seen anyone use it in the wild. I'm interested as well.
Has anyone been paid for these sorts of bounties by Uber? (Short of the $100,000 extortion payout swept under the rug of bug bounties)

It otherwise appears to be an attempt by Uber to get a bit of free crowdsourced pentest.

I'm honestly curious about the HN community on Uber now: does anyone trust Uber on anything at this point? Do you still take any of their research, publications, whitepapers, etc., at face value? Do you trust their code contributions on OSS to not contain malicious attack vectors?
That's really interesting. Methane is pretty bad, but at least biogenic methane doesn't increase the total amount of carbon in the atmosphere.
I think they lose their value in any organization. It's not a hard rule, because there are a lot of variables that could increase or decrease their value. I'll give you an example of each:

1. Decreased value: If a person is the primary (only) developer on a subsystem, any outside code reviewer will be less informed of the subsystem he is reviewing. I don't see any value in that other than get the other reviewer up to date on a subsystem he doesn't actively develop / maintain. I guess you could argue redundancies, but if you have a big system, having every developer understand every part of the system is unrealistic.

2. Increased value: if a developer is working on a new subsystem they aren't familiar with, then the 3-6 month window restarts. The 3-6 month window isn't the time of employment, it's really the time of understanding a particular subsystem.

My point is that doing code reviews in and of itself has decreasing value after 3-6 months. The 3-6 months is the time I'm estimating for a competent developer to familiarize himself with an existing subsystem codebase.

Also, any developer that still has issues after the 3-6 window of the same subsystem is a huge red flag. Code reviews will then just be a crutch for him and the entire organization when the real solution would be to get a better developer.

Also, I'm not saying any communication about code loses value. If I want a guy to look at my code and help me work though something (usually by just listening to me explain it), that has value. I'm generally speaking of the formalized code review that must happen after any coding change. That loses value after a developer is acclimated to the subsystem he has been working on, especially if the reviewer doesn't know as much about the subsystem he is reviewing (and has no need to know). I'm a very anti-hard-process guy. A process must have strong value, otherwise it's just another speed bump.
If you read the linked LLVM documentation, you'll see that any LLVM instruction with side effects that depends on poison can trigger UB, e.g. a volatile store where the poison value is the stored value, not the address.

I haven't tried very hard to write a seemingly safe Rust program using ptr:offset that LLVM will optimize into a crash. It's probably possible with a bit of work; this is basically C's signed overflow UB in a different guise, and programmer misunderstanding of that has caused serious bugs and security issues over the years.
>The reason we need those specific Compaq laptops is that they run a bespoke CA card which is installed into them," explains a McLaren spokesperson to Jalopnik. "The CA card is an interface between the laptop software (which is DOS-based) and the car." If you've never heard of a CA card, then Jalopnik commenter Mike Herbst helpfully explains it's a Conditional Access card. Modern PCs use smart cards or USB keys with special access codes to access sensitive systems, and the CA card was used as custom hardware as part of an integrated system for security and copy protection.
Poor design if you ask me
Inflatable, radiation shielding, light emitting? How.

Edit: Plants and non-human animals wouldn’t appreciate Martian rads either.
One thing people often forget when talking about petroleum is plastics and many other uses that have nothing to do with converting petrol into energy.

Is there a raw material that can be used to substitute for petrol to make plastics or is there an alternate to plastics for mass production and other uses?
I have had this issue with OSX/MacOS from the start. Maybe it is because I am accustomed to the way windows handles maximize, restore, and minimize, but I have always had trouble with those three on my Macs.
It might be worth asking the people maintaining the code base what tools and techniques and hardware they are using.

Also worth considering more RAM. SSD limiting operations implies insufficient RAM.
First, probably was their approach to implicitly require use of Observable objects everywhere.

Second, use of arcane CS lingo and authors writing 10 pages long pages on every known MVC model, FLUX, SCHMUX and etc with weekly regularity.

Third, during transition to Fiber, they went on gigantic increase of complexity by introducing a lot of what can be said to be heuristic rules, and all for non-guaranteed, minor performance gain.
Qt quick is cool, but I never got it running quite perfectly. The examples struggle with the installed libraries, the android support needs a ton of work to set up, they copy the bad parts of javascript ... I like it, but it really frustrates me. There's also little blog-style content about it, which is by far my favorite way to learn.
"Don't ever take a fence down until you know why it was put up."

This is something both anti-regulation political ideologues and entrepreneurs a little too enthused about disruption seem to forget.

The impacts of increased traffic congestion is one of the many reasons that taxis became regulated in the first place.

British Columbia is one of the last holdouts where ride sharing services are still not allowed, and I'm convinced that among other reasons, the fact that the city of Vancouver is so committed to public transit and active transportation is a contributing factor to this.
Rust doesn't aim to make it impossible to have memory leaks: https://users.rust-lang.org/t/memory-leaks-are-memory-safe/5...
COPR = ?

I also can't imagine why Microsoft wouldn't want higher adoption levels...
They don't really need to be radiation shielding or light emitting. People don't need to live there, just plants and animals. And insolation on Mars is sufficient for light.
The problem is you trusted Uber in the first place
When a company does something immoral, why do people always say "well that's bad because it's bad PR"? How about, that's bad because it's immoral?
Yeah, it's fun to some extent; I still remember proving whole Peano arithmetic and then using that to prove functional programs. But doing real-world detail level I would probably go crazy fast; just making proofs some floating point computation does what it's supposed to would be extremely tricky due to bit-level stuff and stretching sparsity of representable numbers that could fit to xyz-bits of floating point.
The famous photo: https://www.nasa.gov/multimedia/imagegallery/image_feature_2...
"They should be the best tool you have for teaching and communicating best practices. "

For christ sake, no. If you want communicate new best practice, do so. And if team agrees, we will follow. Don't ambush me with new expectations during code review and don't keep my task hostage in order to push for your new best practice.

Same with teaching. Teach proactively instead of pretending juniors can solve it and then rewrite all their decisions in code rewiew.

If you have expectations, tell them in advance. It is just unfair to use code review for that.
The big 5 tech companies are Apple, Microsoft, Google, Facebook, and Amazon.

Neither Apple nor Microsoft use Java.

Facebook uses PHP, Google uses a lot of languages but mostly C++ for Search. Amazon does seem to use a lot of Java.
There isn’t a good tax-advantaged alternative if you’re an employee with access to a 401k. If you’re under the income limit, you can make deductible contributions to an traditional IRA but that’s capped at $5500 per year vs $18,000 for the 401k. Plus there’s no company match there. The best practice is to contribute to your 401k up to the employer match and then contribute the rest to an IRA. Once you’re at the IRA limit you comtribute the rest to the 401k.
Ambitious. Sure, but accomplished? Oh if only hard work necessarily equates to that...
Check Gambas if you're interested in a similar language/IDE concept.
It's Linux only, but I thought it was pretty cool for quickly prototyping GUI applications, although I do prefer the more mature FreePascal/Lazarus combo.

http://gambas.sourceforge.net/en/main.html
> but physicists don't publish if they can't accumulate a sufficient sample

What? I would say most published physics is speculative models based on under-sampled phenomena (and that's ignoring the whole explicitly theoretical branches...).

You could argue the practitioners tend to be more realistic about the chance of their models being valid, but this comment still ends up a bit masturbatory.
> git.cypherpunks.ru uses an invalid security certificate. The certificate is not trusted because it was signed using a signature algorithm that was disabled because that algorithm is not secure. Error code: SEC_ERROR_CERT_SIGNATURE_ALGORITHM_DISABLED

stargrave: Please look into this. If you want to push crypto on new users, a broken SSL cert is not looking good.

https://www.sslshopper.com/ssl-checker.html#hostname=git.cyp...

https://www.ssllabs.com/ssltest/analyze.html?d=git.cypherpun...
You should absolutely change your tires regardless of use by age (this isn't just a McLaren thing). Tires dry out over time and become unsafe.
It's not poor design when the only requirement is absolute maximum performance, not ease of maintenance/low cost.
Given a formal proof of a complex system that doesn’t contain any assumptions or mis-modeling is - practically speaking - unachievable...

... then in comparison the time is better spent on something that will produce demonstratable results, even if imperfectly applied.

And that is QA & testing.
Regardless of your personal thoughts, it’s one of the most widely adopted open source projects of all time. And yet you’re asserting that one of its original creators (to say nothing of his other projects) qualifies as no more than a junior engineer?
PWA is not good enough for us due to heavy usage of mobile device camera and picture resizing (client side) for package receiving process in the warehouse. PWA fails to provide consistent performance in such conditions, and issues with bluetooth scanners in Safari/PWA on iOS devices add up. Other than that, I agree Vue.js is superior to React in a lot of use cases, especially for web.
Ask HN: AR goggles to code/devops with?
I've been thinking of getting myself a Christmas present. Has anyone tried to have a number of virtual desktops floating around while doing household chores? Just for a bit of light code review and some CI and chat tools?
Uber’s bug bounty seems like a complete joke.
Right now we know how to power entire countries only with nuclear power. We don't know how to do that with just renewables, which is why e.g. Germany runs coal plants whenever the wind isn't blowing like crazy. It would be much better for our carbon footprint if we replaced the coal plants with nuclear. We can always turn them off once we figured out the whole renewable+storage thing.
Preferably in the most efficient way possible (which is of course subjective). I believe that after 3-6 months in a particular subsystem, the ROI of code reviews increasingly decreases over time.
Most kids don't want to be completely left behind because they're the only ones off social media.
32-bit GPU (Nvidia) era is going to end
Of course it would turn out that the first thing we could grow and eat on Mars would be rocket.
Thank you for your response, but I'm thinking perhaps I didn't explain the reason why I was asking. I understand that Inferno has a different design based on a VM, what I'm trying to ascertain is... why is it better than what came before? The design decisions were more than likely based on a desire to improve on what came before, my questions are about what the designers seeked to improve. In other words, rather than knowing it's a different design, I'd like to know why it's a better design (or to be more fair, what are its strengths and weaknesses)?
Their bug bounty is definitely fishy. If you pull their reports for the last few months, every single one of them at HackerOne have been redacted/locked with no information published. According to HackerOne their vulnerability reports become public after 30 days, but they've given Uber the ability to lock them which keeps everything private.
Yeah, I would love to see some modern N-QAM, FEC spec make it's way into the APRS space. The number of times I see 144.390 key up at S8+ and no packet has to be at least 50% of the time.

Some of the stuff that happens in DMR space is pretty cool, even simple TDMA opens up so many possibilities. You could do Voice+APRS at the same time over the modern repeater network. For instance we've got BawFaw that covers most of SW Washington, would be awesome to be able to run something like that for packet radio.
I'm not sure I assumed developers are driven by the same things. A careful reading of my last sentence did not define what it meant for code to be good or by what process you would be proud of the output, I think that is a product for you, your team and leadership to decide. Perhaps my use of the word pride was too strong, the core of my philosophizing there is that software development on a team is a social endeavour and that code review can be a very effective alignment mechanism.

Someone further down the page suggested that the style nitpicks arise from a lack of understanding and familiarity with that piece of the codebase. I think that is often true and a factor to be considered both when allocating code review and when setting expectations regarding code ownership and cross-functional understanding.

I've also provided some suggestions for how to tune down the "95% style nitpicks" elsewhere on this page - it is a problem, but with appropriate tooling and expectation setting, it can be reduced to a small fraction of total code review output. It would be dysfunctional for a team to spend time on that stuff when we've all agreed it isn't high ROI. I agree that code review can be done very poorly, but your observed ratios are not a fixed property of the world of code review.

Let me be clear: I am absolutely not advocating for a process that motivates nerding for the sake of nerding - I push back on a whole wealth of that sort of behavior. I am a business person motivated by producing sustainable teams that produce real value in the form of solutions to problems. I just feel that is a high-dimensional problem and certain kinds of technical debt can come at extreme cost and can, at times, if done correctly, be mitigated with processes like code review.
Nothing in that statement is sexist or ageist.
You're probably down voted because actual discussion would lead to the Samson Option.
You seem to know about this. Am I risking anything driving my 6 year okd old winter tires for 3 years non stop (winter and summer, 15k km yearly)?
6-7 years ago, I would have been saving up for this. That was a very different market for video production professionals.

I never liked hacking cameras that were not made to be hacked, but this one is. It’s not the first, but the other projects appeared to be barely getting by.

The sad part is just how long this has taken to come to fruition, and how little sense it makes economically at this point.
> they can't make their own sensors (e.g. RED Dragon) so they need to use CMV12000 which is a sensor for scientific and industrial applications - fast, but not optimized for image quality

> from the likes of RED, Canon, Blackmagic etc

Guess which sensor in in some of BlackMagic's offerings?
> After trying (and failing) to wrap “executable” ducktape around a Python script using PyInstaller on Windows

Funny. I just started working on an open source solution to that exact problem: https://github.com/mherrmann/fbs
Related in a limited fashion:

https://docs.microsoft.com/en-us/dotnet/framework/data/adone...

Then there's this write-up of someone replacing rethinkdb with postgres for live queries - (including a link to some code)

http://blog.sagemath.com/2017/02/09/rethinkdb-vs-postgres.ht...

Have you any plans already of how you will go about this?
In terms of the cons, I find that if the output code is good and the team as good practices regarding style (a linter and styleguide), reviews for unobjectionable code are a breeze, and often take minutes for reasonably sized changes that have no issues.

A style guide and linter also remove the arguments about minutia. Google's python style guide is a lot less strict than the go or java styles, for example, and even still most of the style comments I make when reviewing code amount to "be internally consistent" about something, and those are nits.

And that whole "reviews take 5 minutes" doesn't mean that they aren't useful. I often find something that is either confusing, or a typo, or dumb mistake/overlooked thing or a non-idiomatic way of doing something, and leave a comment expressing that. The review still takes 5 minutes, but I've caught a bug or a bit of technical debt later.

As a code-writer, I have more or less the same opinion. I would flatly refuse to work somewhere that doesn't do code review. It makes working in the codebase difficult, and makes personal development more difficult.
> Neither Apple nor Microsoft use Java.

From what I understand Apple uses java/scala fairly extensively for backend services.
A bit off the topic but I always wondered why social scientists need funding or even a university for their experiments. I mean the kind where they put 20 people in a room and show them some pictures and ask them some questions. What resources do you need?:

Time - do it as a hobby so it's limited to people who are passionate about discovering something, not just trying to rack up points.

Access to human subjects - get people off the street. Universities can make access to student subjects easier but they're not representative of the world's people anyway so it's not that valuable.

Money to pay the human subjects - save up? People who're passionate about cars, for example, somehow find the money to build modified cars and don't need funding.

Ability - With the oversupply of researchers, maybe just leave it to those who can do it under their own steam? Hopefully undergrad degrees taught them enough to get started. This article says that university researchers aren't doing it with skill anyway but with luck or cheating.

Motivation - if nobody can be bothered investigating some effect, then maybe it's not really that interesting anyway and there's not much value in studying it?

What am I missing?
Having first hand experience with the VA I can't say I'm surprised, but really it doesn't matter that it's the VA, because I think most companies doing iot things already are likely going to face failure on their project as well.

In this case I'm mostly thinking about the horrible security environment of the iot ecosystem, especially cellularly connected ones.

"VA officials worried that the department’s $543 million contract with Hewlett-Packard Enterprise Services to implement a real-time locating system, or RTLS, was careening off the rails"

Wow. Let me guess, good ol boy contract kick-back where the good ol boy can't deliver as promised. It's a classic American tale. Great thing the government bid system is blindingly fair and egalitarian. Yup, that's it I bet.

"VA officials have said work here stalled about 18 months ago due to contract issues"
In my view it's because immorality only really affects a company if it's perceived as immoral (i.e. is a PR issue)
I doubt that's the goal (or at least if it is, it is shortsighted). There's still a benefit (to the police) of being able to say "Here's 100,000 images, of which we strongly suspect some percentage are abusive. Show me those images which are _probably_ illegal", even if just in time spent.
I first tried going full on .Net Core with an ASP.Net Core project with Docker and I was going to try to use Kubernetes even though we were going to stick with Windows Servers.

It was overly complicated and there were so many gotchas I found in the proof of concept that I did, I backtracked and went with the ASP.Net Core Framework (aka Asp.Net 5) using Kestral on top of .Net 4.6 and using Hashicorp's Nomad for orchestration.

I'll try again in a year....
But so do most other programming languages and frameworks.
You are a great child.
You should not be nuked because those are real questions. I think we have organizations (not legal) which kill anybody attempting the variations of what you describe.

We sleep soundly because there exist men willing to do inhuman things to ensure our security. It's unpleasant until compared to the other options. That's what genuine heroism is like. When Putin is praising that organization he is thinking of something like this. We live very sheltered lives I think.
Bafflegab, unfortunately — an indergraduate’s effort to satisfy the minimum page length requirement for an essay.

The promise of a fresh perspective is left unfullfilled.

Thanks for sharing it, though.