skysight-inc/HackerNews huggingface dataset:
> Cons:

> 2. Petty arguments over style rather than technique. It can devolve into minutia / trivia.

This can be mostly addressed by using a linter. In our organization, we have a rule that if there is a glaring style issue, we ask whether the submitter had actually run the code through the linter before submitting it for review.

On the other hand, if the linter does not complain about some code, but the style it's written in is not agreed upon, we update the linter configuration to handle that case if the rest of the team agrees. Otherwise we leave the code as is (assuming it works as its supposed to).

> 3. Once a developer "gets the idea" of how the organization wants coding done, it becomes more of a seemingly pointless routine.

I find that there's always room for improvement in terms of how things are done and those things could be done in a code review. The other thing is that its always a good thing to have at least one other person look over a change just to make sure that its correct and something obvious wasn't missed.

Edit: s/submitted/submitter/
Good assessment. To summarize the argument, Vue.js is just as good and some would argue better than React for web development, but the React ecosystem really puts it over the top, especially React Native.
This is a bit complex, but for what most people think of as WCF (enterprise SOAP APIs) then it is not supported on .NET Core. The W stands for Windows after all.

However, the ASP.NET Core MVC framework supports Web API and this was originally part of the WCF REST services. Of course, you can still interact with SOAP endpoints (served by various frameworks) as a client, as pointed out elsewhere here.
I truly love Vue and hope it evolves and spreads everywhere.
My teams also assign code review "in addition" to the regular workload, but this is always in the context of an agile team effort: we get done what we get done [1]. A developer takes a story and works on it until it is solved (or splits it appropriately), then another developer (or a few) are expected to do review.

--

[1] I might be measuring productivity with story points in the background, but there is no "scheduled workload," this is merely an averaging/planning exercise.

The (correct, IMO) managerial effort to improve individual productivity is much softer and more understanding than that and comes with the understanding that your output takes many forms. Some of my best developers directly complete almost zero stories in a sprint because their time is spent on code review, pair programming, direct assistance and architecture discussion.
You would use two buckets in this case. Input bucket gets consumed by worker processes to do the transcoding (and validation) and then they upload into the output bucket. The output bucket is what you serve to clients (hopefully with a CDN in front).
Thank you for posting that. Unlike the top-linked article and the LibreMesh docs, the Althea site does a pretty good job of communicating what it intends to provide, making the useful distinction between user nodes, intermediate nodes, and gateway nodes and their different responsibilities.

I'm dubious about the effectiveness of their plan to use escrowed cryptocoins to pay for bandwidth, but I was intrigued enough to sign up for email updates.
Don't all modern DSLR shoot video?
I’m the founder writing code (but not the only technical person) for my three person startup. In October I started migrating our MVP from server side templates to Vue, given we had direction and traction on a product line that justified the time investment. It’s turned out to be a great decision (although likely one that could have been made with react as the choice as well).

My “success story” is how Vue helped me to massively improve our user experience in low bandwidth or high latency environments. Our startup is trying to reinvent the ways that companies approach their review process, and one of the things we do is run a workshop on delivering actionable feedback during the review cycle. We have users log into our app during the workshop, and this often happens in conference rooms over congested WiFi. Our MVP used turbolinks, so it felt generally “snappy” during normal use, but could feel sluggish if moderate latency was introduced (such as a congested router).

Since I completed the rewrite to Vue (which took only about two weeks because of how simple it was to pick up, even for a non frontend person like myself), we’ve had multiple launches that both would have likely bombed had we not done the work to move to something less dependent on a tradition client -> server -> client response cycle to render the next “page”.

Either way, I’ve become an advocate for vue. I love single file components, love the documentation, and am very happy with the community libraries. All in all, I’m very bullish for Vue in 2018 as a happy new users.
Is this serious question? Yes, people are still saying the same thing about test-driven development.
Whatever are the odds, I can't imagine nukes helping us in either situation.

A digital superinteligence (should I expect it to be organic?) will be either very concentrated or backed-up everywhere. On the first case traditional explosives will give us better bang for our bucks, and lead to less collateral losses. On the second case, nuclear weapons would destroy us much sooner than the AI.

On the case of aliens, the entire problem is how to reach them. If we can get some weapon into them, yes, a nuke would probably be marginally more effective than a lump of lead, but not by a large difference.
You want to minimise the adversary's chance to put in place proper evacuation or countermeasures.
A couple of useful links:

https://github.com/carp-lang/Carp

> Carp is a small programming language designed to work well for interactive and performance sensitive use cases like games, sound synthesis and visualizations.

The key features of Carp are the following:

* Automatic and deterministic memory management (no garbage collector or VM)

* Inferred static types for great speed and reliability

* Ownership tracking enables a functional programming style while still using mutation of cache-friendly data structures under the hood

* No hidden performance penalties – allocation and copying are explicit

* Straightforward integration with existing C code

http://blog.veitheller.de/Carp.html, HN discussion at https://news.ycombinator.com/item?id=15778530
Yup. Bittrex is a good companion
> jazz background

Jazz physically gives me headaches. I don't mind the music, but after a short while I tend to get a headache, even if I didn't notice it and it was playing in the background.

Let's just stick to the goal being silence, ok?
C# is a great language and I love using it (especially compared to Java), but right now the Microsoft stack is prohibitively expensive compared to the common stacks for java, ruby, and python. .NET Core is a great step in the right direction, but it is going to be a long time before parity with other ecosystems is reached and unfortunately enjoying writing the code is way less important than having the libraries I need to interact with modern web technology.
It's pretty awful in about any regard in my experience. What would be the reason to use it over MVC?
I can’t imagine any reason to skip code reviews in any professional development. Someone is paying the team to produce professional code, finding out well after the fact that one section/contributed failed that test is unacceptable.

Code reviews shouldn’t be lots of overhead. They shouldn’t devolve into style critiques. They should be the best tool you have for teaching and communicating best practices. Reviewing a more senior devs code can teach a junior a lot, and occasionally catch significant errors.
Would tend to say the opposite. Google kept the PVC a secret until found in the pixel 2. We did not know about the TPU until used in production for a while. We did not know about the gen 2 TPUs until done. There is a long list of Google doing things and never sharing. Kind of the opposite of what you suggest.
To add to that, this pension (and many others) was structured such that payouts are non-linear based on number of years worked, so for example, you might get:

0-5 years worked: no pension

5-10 years worked: 5% pension

10-20 years worked: 20% pension

30+ years worked: full pension

By preventing workers from being able to work the full 30+ years, they never had to pay the full pension. One of the workers in the story mentions receiving 1/5 of full pension after being laid off due to the closure.
thats not even close to the final price. they'll probably drop another $250 mil then cancel the project. they dont even have this running in 1 VISN and there are over 20.
Oh right, thanks for the explanation.
I follow your argument, but I think that's certainly not what the author of the article was intending.

And that's a very hard number to come by, because as I've argued you would have to factor in all other reasons why a pension might have to be paid out longer or not at all.

Certainly "3 years of average payout" must be completely and utterly wrong because this number includes infants etc which were never employed. Infant and child mortality has an enormous impact on average life expectancy.
Rust actually has undefined behavior that is triggered by code outside of unsafe blocks, depending on how a result is used:

https://github.com/rust-lang/rust/issues/33813

This basically exposes LLVM's poison semantics (a kind of deferred UB) to Rust code:

https://llvm.org/docs/LangRef.html#poisonvalues

Code in another module that doesn't even know it is calling an unsafe function could trigger UB by using this.
Ethical companies seem to have either shut down and returned the money (giving employees a few months of severance) or pivoted. Pivoting seems much more common.

Some unethical companies just keep going until the money runs out. It's hard to know who falls into this category from the outside, though.
This is similar to the conclusion I came to after doing my PhD in a CS department that had lots of people enamored by formal methods: that the usefulness of it is inversely proportional to the complexity of the project to be verified.

Sad that apparently hasn't changed much in the 20 years since.

I say "enamored", because formal methods seems to me like a field that gets a lot of attention because the possible outcome of it is so damn attractive: if we indeed could easily prove software correct, that would be the biggest advance in software, EVER. But is a bit of a fallacy that just because the imagined end result is so elegant and desirable, that there must be a path to it.

Also, any gains that can be claimed by formal methods are hard to evaluate in a vacuum, as using any other techniques that involve spending 10x more time thinking about / working with some code can possibly have equally beneficial reductions in bug counts. Most software that has undesirable bugs is such because no time/money investment is deemed worth it to make it better, not because formal methods is the only way to improve it.

I find it funny that meanwhile, mainstream software is going the opposite direction, with ever larger systems written in dynamically typed languages like JavaScript and Python, or overly simplistic static type systems like those of Java and Go. You'd think if formal methods was our far away desirable future we'd be incrementally moving in that direction by using more expressive type systems (Haskell, Rust..) and maybe even dependent typing. The invariants that can be encoded in such systems can rule out usefully large classes of bugs with way lower effort than formal methods, but somehow movement on that front is slow. If so few people care to even grab the low hanging fruit, why do formal methods people think we can jump from chaos to order in one step?
Seattle airport had some live music in a large public space, and it was a great shared experience. Piped music is not an experience in the same way, not in the slightest.
Technically yes, but it's not as practical as the high end video cameras mentioned above.
React changing their license probably saved them.
My web dev office was going to transition from them until they changed it.
Sometimes I wonder if there are any internet companies (startup or otherwise) that do customer support. With numbers like that, it's hard to imagine one of those users getting even one second of attention with any problems they might have.
In a way C++ is using higher-order functions conceptually too for polymorphic runtime dispatch. Because it uses vtables, which are lists of function pointers--essentially the object doing the dispatch is a HOF which calls one of the functions it has a pointer to.

All this is just made explicit, and the boilerplate OOP mechanisms stripped away, when you just directly pass first-class functions around.
You can set your own music to whatever volume you want, instead of being forced to turn it up to overpower the piped music...
Most do so kind-of-poorly, usually for dumb (tax classification and product differentiation) reasons. I switched out of the Canon ecosystem for a few reasons, but the biggest reason I went to Panasonic was video. The GH4 (and to a lesser extent the GH3, both of which I own) punch well above their weight as far as video goes, particularly for live video, but most "DSLR"/consumerish-mirrorless cameras are a good few steps below a dedicated video camera like anything from RED or even the BlackMagic Cinema stuff.
No. Again, you are completely mischaracterizing what they do. It is clear you are not interested in a good faith discussion on the topic, and would rather just rant about government. Feel free, but I won't partake.
I'm sorry but I can't make any sense of what you've written.
Electron is chic because it looks nice and it feels nice ...everywhere. Until it does not and then the costs of doing it in smh else are too high
I believe the correct terms are ambitious or accomplished.
It is a chicken egg problem really it is the same like Nim, Crystal etc
Simple ways to reduce stress
I have never even heard of this one. <shrug>
The application in question is afaik a browser. As far as I ‘be been following this disaster, the client spins up a local webserver which then is accessed with your systems browser. So they have to use the cert store that the browser uses - which is the system store for some of them.

The problem in this case is not the cert in itself, the local webserver needs the private key. It also uses a non-local domain (bealocalhost.de or something akin to that) which resolved to 127.0.0.1. This is another design brainfart - it assumes that no webserver is running locally, the DNS is in no way protected, making it trivial for anyone who controls DNS to reroute that domain and since they have access to the key, MiTM is trivial. :sigh:
Baby steps with CNTK and F#
I mostly use the triggers with the webhook action and call one of my webtasks (webtask.io). The free tier of 1 req/sec is enough for me
Turning a rifle into a shotgun on this case is a good thing, and may completely solve the problem.

But, anyway, unless we wait way too much, it's better to deflect an asteroid than to break it.
I would use Xojo for a "successor".
Charlie Puth Powerusing the iPhone, Mac to Make “Attention”
Um, it seems to me you'd direct your submarine close to the coast of a city and your missile launch would not need ICBMs.

In fact, I am worried about TacNukes - like the kind we see in James Bond movies - being smuggled INTO A CITY!

https://www.wired.com/2002/11/nukes-2/

Here is an article about loose nukes.

North Korea has ALREADY given Syria nuclear material to build a functioning nuclear weapons facility. Google "operation orchard".

I am worried that, as soon as we attack its regime, some sleeper group would use nukes somewhere.

And what do we do in general with rogue nukes? How exactly are they accounted for across every country?
My typical use case doesn't need native apps - a PWA is good enough for me. I will not comment on speculation about the compile-to-native feature because personally it is irrelevant.

I can say that as you I prefer Vue over React and some of my personal reasons are:

* I like opinionated frameworks

* I don't like to mix Javascript and HTML - I can handle a Vue template to any designer but I would not trust a JSX file to a non-programmer.

* Vue is easier for developer onboarding - with Vue the gap between a junior and a senior developer is way smaller.

React may be better, I don't care, Vue is easier for my development style.
You're Spot on, the problems aren’t unique to IT, it’s a systemic policies / process / procedure failure.
Electron is pushed by JS devs because now they can target another platform with their toolset. The JS crowd is rather large. Sadly, Electron style apps aren't going to go away any time soon.
OK, I came here actually wanting to read the article.

First thing that happens is a chatbot pops up wanting god knows what with an annoying notification sound. I find its quasi-transparent X close button and click it, only to have a huge popup show up literally a second later, asking me to fill in my email for god knows what other reason.

I left the site. Fuck this.
The World’s Top Banana Is Doomed
The board should go to the shareholders with a plan or ask for process to be started to approve of a plan do go forward, which might mean give a pro-rated portion back and go off in one or more new directions with the balance - if any?
These are the company building a RISC-V processor from an FPGA I think.

Edit: a downvote? It's true, see this presentation: https://www.youtube.com/watch?v=PyJ8PoASWdw
Is there any foolproof way of detecting if some video or audio is a commercial or not?

A TV tuner that just replaces commercials with a placeholder image and a countdown to when the break is over would make broadcast TV just about tolerable for me. (time-shift, and skipping past commercials is a better solution, but there's some things you want to see live)
It's assumed that a submarine can travel in the ocean for long periods without detection. I don't know whether this is still considered to be true by military strategists, but it's a large part of the motivation behind having nuclear-armed submarines in the first place.

A submarine is at least pretty stealthy, but the heat signature of a missile launch is impossible to hide.

Another way to look at it: the satellite systems described in the article (SBIRS and DSP) are optimised for early detection of a launch. So when considering the deficiencies of those systems, it's correct to consider a hypothetical adversary who optimises for the opposite.
The Project Orion people had extensive calculations on how to send a city-sized ship to another star on a ~100 years trip with nukes.

It is laser propulsion that is techno-magic. Even today. I won't register on whatever site to read yet another article on that, but I do bet neither the lasers nor the sail on this one could be made today.
It’s become a common practice due to the changes in how browsers handle local, expired or self signed certificates. The “right” answers (use public CA, setup a local PKI) are complex and deliver low value.

PKI is complex, and certificate expiry is a major source of outages.
Looks nice: agreed.

Feels nice? Try running an Electron app (for example atom or VS code) on a 4gb ram celeron (like the one I have at my 9-5 work) and I can guarantee that you won't like the feeling :/
CHDK link for those interested: http://chdk.wikia.com/wiki/CHDK
My point was a response to the parent comment:

>"Sadly Indonesia doesn't have the near limitless resources of its old colonial owner that keeps Amsterdam/Holland from sinking"

When in fact fact it does have the resources to build a Delta Works-like system similar to the Netherlands.
Track Santa's Eve Flight Today with NORAD
It probably depends on the work you are doing. We do test harnesses for hardware and most reviews are the result of a lot of experimentation and learning about protocols. In order to understand that code you need to know the characteristics of the device you are interfacing with. This may take weeks for a reviewer.
yes, without all of downsides of traditional DRM solutions
Probably they're trying to avoid "not secure" warnings from browser which are displayed if http-served web page contains password input fields (Chrome 56+, since October 2017).
Same with my Pixel 2 XL. So far the best smartphone I have owned. I now prefer Android over iOS and the Pixel 2 is as smooth as any Android phone I have ever used.
Do Vue templates play nicely with Typescript? That's something I love about JSX -- "it's just JavaScript" is an incredibly sublime feature. I know you can use JSX with Vue but I'm skeptical since it's a first-order feature with React.
Seems to somewhat fit the defition, if you squint a little

> A Ponzi scheme is a fraudulent investment operation where the operator generates returns for older investors through revenue paid by new investors, rather than from legitimate business activities or profit of financial trading.

https://en.wikipedia.org/wiki/Ponzi_scheme
So it might work! Can we boostrap a real, nutrient-rich regolith and ecosystem from scratch? That would be some amazing terraforming - and some major value for mankind.

And here I thought The Martian's most unrealistic part was growing the potatoes.
From the comments:

https://www.wsj.com/articles/amazon-makes-major-push-into-fu...
A Book Recommendation for Bill Gates: The Story of PLATO
I'm afraid React is eventually turning into Angular. At some point, I felt that Angular is somebody's PhD work exploring arcane computer science concepts, not a piece of software for practical use.

React gets closer to that with each year.
"Men alleged to be part of a child-grooming ring in Rochdale were never brought to justice because the evidence of teenage victims was not pursued, according a former police officer"

http://www.bbc.co.uk/news/uk-21925205
I'm using it to save taxes, because I'm not sure what are the alternatives. You're comment makes me feel I should be less ignorant: any good online reading to suggest?
Re: type annotations, it's a best practice in OCaml (and at least possible in F#) to provide interface files for your modules. The interface files capture all the type info and documentation, and the implementations stay succinct. Best of both worlds.
Yes. The USA should quit meddling in places it doesn't understand at all.

"Don’t invade a country if you are too lazy to learn the language." is a good rule of thumb here.

http://www.pieria.co.uk/articles/why_the_worlds_biggest_mili...
Google and Apple have the only two mobile platforms so of course that is where focus will be.
What to do about welfare
> think about different systems to support everyone in the upcoming job armageddon.

Would have been nice if the opposite side articulated what exactly that they were thinking of doing or at-least some vague idea would have been nice. Repeatedly saying "most qualified in the history to run as president" is not very convincing.
I use time tracking and activity tracking for my own edification, but that information is only shared with clients in the form of an invoice.
If you think about it that way, Chicago and Orlando are probably OK if you choose the right area.
For me, the problem with formal methods is that a prerequisite is a (formal) specification, and I've never seen one of those in 20 years of software work.
Oh, God. Excel is the bane of my existence. It does all kinds of crazy stuff that baffles me to no end. I'm sure it all makes perfect sense to an Excel expert but for the casual user who only has to use Excel a few times a year it's a battle with the program. Stuff like interpreting plain numbers pasted as "text only" (example 1234) as dates. And you have to pay close attention because it doesn't really tell you "hey I'm changing what you entered."
Agreed, that part was lengthy as well, seemed to be way too many steps, but with the amount of users they've acquired that process doesn't seem to be an issue.
Arc: A manager for your secrets