skysight-inc/HackerNews huggingface dataset:
>For something as important as an election, it should be simple enough for people to understand the process and believe in the result.

In my county in California, the first voter to arrive has the responsibility of verifying that the ballot scanner is empty and that its printout reads all 0's. That person then serves as a witness to the poll workers applying tamper-evident seals to the scanner door and data module.

This takes no more than two or three minutes to accomplish, and anyone with reasonably working eyeballs can carry this out. You lose this scrutability when you introduce cryptographic proofs and multi-step algorithms into the process.
He is not saying Java caused it, just that the priority was cheaper labor, and a more popular language makes that more likely.

This is in the context of software development in general, not this specific project per se.
Plus familiarity with using a gun.
Seems like a good personal marketing piece. I’d consult him to help get social media posts viral
> It's a sad state of reality, because it drives down the quality of software to the common denominator of fresh junior devs, which is not much.

There's no reality here, just myth. That switching to Java would drive quality up makes at least as much sense as it driving it down.

If you're referring to the particular languages, then the reality is that no big effect has been found for the choice of programming language on software quality. As lack of evidence in favor of a big effect is evidence of its lack, the most probable explanation is that no such effect exists (it's possible a small effect exists, but we don't know in which language's favor). And, indeed, while there is a theory explaining (and even predicting ahead of time) why there is no big effect to the choice of the programming language, not only is there no empirical evidence suggesting there is such an effect, there is no theory to predict it, either. That language has a big effect on quality is, at this point, no more than wishful thinking among a minority of developers who are big programming language fans. It's a bedtime story. (I am not saying that language didn't ever have a big effect or that it never will, just that both theory and observation show that there isn't one currently among "reasonable" languages in common use; also, I have used and I like both Java and Clojure)

And if you're only referring to the priority of making the project more accessible, then I don't understand your comment at all. There are many, many more experienced Java developers than experienced Clojure developers, and experienced developers are at least as likely not to bother learning a new language in order to contribute to a project (although perhaps for different reasons). Picking a popular language makes the project more accessible to experienced developers.

What has been shown to drive quality up or down is process. If you have a good process, then making the project more accessible can help, and if you don't then you're screwed anyway.
For the U.S. and China, it’s not a trade war anymore – it’s something worse
I'm usually looking for two kinds of switching, most implementations support one of them. Switching on a list of conditions in priority order like CL's COND, and switching on a value.

Simply making the value optional and injecting it in specified conditions if present would allow using the same construct for both.

Note that this may well be possible in P6, most things are; but I have yet to come across and example of COND-behavior, they're all switching on values from what I can see.
Sad to see it happen, however it is yet another example how platform languages always win in the end, even if due to their nature and market size they tend to be more conservative regarding feature adoption.
also they can still have hybrid clojure jars if needs be
Google's sells advertising.

The idea that two-sided market can't have market failures because one side gets free services is not very strong one.
Right, but Switzerland still has the draft, and consequently more awareness about gun safety among owners, as well as inflated gun ownership statistics because you are required to take your gun home with you. And while guns are relatively easy to buy, ammunition is much more controlled.

Switzerland also has a lot more social security than the US. I agree that it's more complex than "guns are bad", but using Switzerland as an argument for gun ownership is just glossing over the details to come up with an artificial example where gun ownership doesn't result in increased violence.
What if Clojure is a language that bodes well especially early in a project’s lifecycle?
I pretty much agree. I big part of the reason why I personally like Google is because they, or at least a majority of their employees is actively progressive. Even if that’s just PR it’s still a nice counterweight to the mountains of companies who are just completely neutral or conservative culturally. At the same time, they and facebook facilitate the spread if right wing extremist ideology to some extent.
The larger problem is the toxic gases being released.[1] For my latest safety training in the maritime industry the handling of lithium battery fires was essentially put yourself upwind and let it burn it self out to prevent any exposure.

[1]: https://www.nature.com/articles/s41598-017-09784-z
While it is true that Java is statically typed and Clojure is dynamically typed it is perhaps one of the less important differences between the two languages. If you in fact would like to add a static type system on top of Clojure there is a way to do that: Typed Clojure.

https://typedclojure.org/
I understand it being an edge case in testing but I think there is a design issue here with “forever authorization”. Once the device is paired with Alexa I don’t see why Alexa would not still need to get authorization each time it accesses the device? It would seem like once the device went to another account Alexa would attempt authorization and then fail.

Authorization is the problem with a lot of security problems today. I don’t think it should be a corner care, it should be in the initial design of most things (internet of). Calls to banks, use of CC, and now IoT.

I read the resolution from wyze and while I’m happy they patched device associations I was looking for the term “authorization” and didn’t find it. I wish this term had more weight and meaning in the practical use cases we see as consumers. And I wish it was in the initial meetings for us tech devs.
@AnaniasAnanas: And someone with less money than you can use your software source code "as a reference" when writing their own open source reimplementation. They won't put your name in the copyright notice because they didn't use any of your code, they only used your code "as a reference" when writing their own.
Before the Internet, you had BBSes. And hundreds of years before the BBSes, people carried out intense friendships via pen and ink.
With any sentence that contains a "can't think of people who X" structure, you should realise that people you know and talk to are people who think like you. Exceptions don't break the rule, as always – if you do make a statement like that think first if your sample is representative of the population.
Building ETL Pipelines for Kafka Data (Guide)
Online Reputation Management Stats
> Also, someone using Java does not automatically make them dumb cheap programming labour, same as someone using Closure is not automatically going to be a 10xer who has memorised Knuth.

I'm not claiming that. I'm claiming that Java has a long history of enabling factory-farming software development, whereas Clojure doesn't lend itself to this style. I mean that in the sense that an army of cheap labor with shovels can, in principle, do the same job as a few trained operators in construction machines. The physics of dirt is the same, and so the job done is essentially the same - just some tools let you do it faster with fewer people. And then, the quantity (or lack of it) has a quality of its own - the more people you engage doing smaller and smaller pieces of work, the more your work becomes about coordinating people than doing the actual job.

(I'm aware that since version 8, Java is growing to be a quite decent programming language. This somewhat weakens my criticism, but not all that much.)

But yeah, I'm also claiming that ceteris paribus, the pool of Clojure developers will yield you higher-skilled programmers on average than the pool of Java programmers - simply because everyone and their dog knows some Java nowadays, and some Java is enough to make some progress in factory-farming software development, whereas Clojure is somewhat atypical and requires expanding your competences beyond the very basics.

(Or, in other words, I'm claiming that the distribution of skill of Java programmers is wider than that of Clojure programmers, with the latter having higher minimum and mean values, and comparable max values.)
Yes. It basically turns a reverse engineering task back into regular "forward" engineering, except you are programming with z3's symbolic variables.

Here is an example: https://anee.me/solving-a-simple-crackme-using-z3-68c55af7f7...
Every time I start to think about writing a technical book, this is what stops me. The sheer amount of time you'd need to spend writing it is staggering.

On the flip side, once you've published the book being a noted author may present you with certain kinds of opportunities that may not have been available before. That perhaps is more valuable than the revenue generated from the book.
> The ecosystem has moved on

Just ouf of curiosity, what tools are people using instead of Storm?
Why on earth did they put a car full of lithium ion batteries in water? Surely that's just risking a rather spectacular reaction
What if the solver both fails to find a counterexample and fails to conclude there isn't one? (i.e. it times out)
I've thought the same thing. But also the results speak for themselves: is Slack actually struggling because they don't have native apps? What's the cost to their business bottom line? What motivations would drive it to ever be a priority?

I think this is an example of a community of nerds forgetting that we're something like 0.1% of a product's userbase.

I think the perpetual anti-electron sentiment is a strong example of how you need to be careful not to listen to just your most vocal customers. Otherwise you might triple your engineering load without even a fraction of practical, real life, measurable benefit.
Because until JVM turns into KVM, Kotlin is just another guest language on the JVM, without much to add as a company pushing their agenda and trying to use the JVM as a lever.

KVM might well turn out to be ART, but that is the extent of it.
Friendship formation is different online than in real life
AdSense and AdWords work a bit differently and aren't exactly "real time bidding" in the industry terminology sense of the word. By that I mean they are real time and there is a bidding element, but AdWords for example stays under the Google roof and typically does not go on a real time bidding ad exchange. Contextual targeting is definitely kosher under GDPR, so Adwords and Adsense likely fall under that umbrella, for the most part.

AdX is Google's ad exchange. Over there, you do see a lot of data. However, I would bet that the personally identifying data is mostly scrubbed in the EU. User agent and page URL are not identifying enough, so they're probably included in the data.
I think it’s very difficult to motivate going out of your way to hire decent devs that know clojure and java only to throw away the clojure some time down the road.

Begs the question, why not just write it in Java? Then at least its more likely to be a refactor down the road rather than a rewrite.

I think clojure ought to be a production ready language that scales well. That’s what it was designed to be. However lisp seems to dichotomise devs into those that get it and those that don’t and thus alienates many would be team members.
You can easily get it on Java with PMD and other static checkers.
Key quote from the article:

What might this mean for everyday life? Well, it suggests that the friendships we choose to pursue from online profiles are much more likely to match our ideal standards for what a friend "should be." However, when it comes to choosing friends in live contexts—either in person or in an online chat—it seems we toss ideals out the window and rely solely on instinct.
Instal PMD and you are set.
Why stop at the ISP level? Have a system that allows the user device to negotiate a connection with whatever services are available. The service could offer bids from providers which would have to specify a service level and price point. Then have a second price auction for every unit of time (say 10 mins). The user tunes their device to get the level of service and price they want. A contract would then consist of a VPN provider who would make bids on your behalf for a fixed monthly price.
1. Language problem:

if (this.prop != null) {
this.prop.something() // does not work
}

this construction works for local variables, but not for properties. Yeah, theoretically it could be modified by another thread or function in the middle. In practice it does not happen and I'm forced to use terrible code like

this.prop?.apply { prop ->
prop.something()
}

(this example could be written as this.prop?.something() but that's not the point, usually it's harder than that.

2. Interoperation problem. A lot of Java code does not use @Nullable annotations, so all types are just that: platform types. So Kotlin nullability adds nothing to that.
If you are talking about WW2, the important parts are the events leading up to it.

And the Weimar Republic, before Hitler came to power, did have strict gun control laws.

Would people owning guns in the Weimar Republic (like in Switzerland) have prevented WW2? We don't know, but it is at least a legitimate question.

But certainly the uprising in the Warsaw Ghetto, which at least saved some lives, needed "illegal" guns.

So in general I don't get Europeans (I am one) who turn up their noses at the 2nd amendment.

Millions of people have been killed by governments in Europe. Governments are, and always have been, the real danger.
I guess you mean Java here, and yes some of them have a JEP defined.
Maybe, but learning a new language by contributing to a large project built in that language is asking for trouble. Programming languages aren’t just syntax and stdlib. The relevant idioms and patterns may be significantly different. Even making small changes can be hard and intimidating.

And then, even if you wanted to learn something new, to a lot of people, it matters what that something is. Unless the person is really set on contributing to Storm specifically, then the barrier of Clojure is still significant. They may prefer to spend their new language learning bandwidth on something with more momentum.
It's important to remember that Marcus Aurelius is the only Stoic who thinks this. For all other Stoics, ethics is grounded in metaphysics and theology, not independent of them.
Many cs courses teach ML style functional programming, not Lisp or Clojure
Maybe you can find an application for ML at your current employer. Gain some experience without starting from the bottom.
I agree. If an article doesn't meet the guidelines [1], then please don't upvote it.

[1]: https://news.ycombinator.com/newsguidelines.html
How exactly would that work? Should the government offer to buy it for the asking price and then release it for free? What if the asking price is overly inflated because the government with it's endless budget is buying it? What if the government prefers to buy products that were developed in a variety of states and by a variety of people with different skin colors and chromosomes?

Or should it be illegal for researchers to sell these type of product? That will cause all of the brilliant talented people who need money to look elsewhere for work. I wonder if they will be able to get a competent team.
That's just not true. If I'm writing simplest REST service, I have to return JSON responses. To return JSON response, I have to write class corresponding to that response. And that will be data class. If I'm interacting with database, I'm writing data mapping classes. And that will be data class. Those are normal code that every developer writes every day. If you think that it's anti-OO, then I don't care about that OO. I care about writing performant, concise and extensible software.
I have one system I still use chrome on - my late-2013 Macbook Pro.

The reason I use chrome as my main browser there is because Firefox and Slack do not seem to be friends on MacOS. I use slack in the browser rather than the native app and FF seems to get copy and paste functionality all messed up.

I would use Safari, but some quirk of the office webmail (Outlook of some sort) means that email from Safari gets flagged and blocked as potential spam by an outbound mail server :/

But everywhere else, Android phone included, it's Firefox because they don't pull these kinds of shenanigans.
I think a simple rule is this: if the topic has to do with the balance of liberty and security, it's going to be controversial.

But not necessarily because there's true dissenters in the simplified binary "you're with us or against us" way. But because it's a topic with no objectively right choice. Liberty is genuinely important. Security is too. Society and Government is largely about the balance of those two.
Just because nerds complain doesn't mean doesn't mean "non-nerds" aren't suffering from the same problem except they don't have the technical knowledge to blame it on Slack using Electron, so when their computer is sluggish or runs out of battery in half the expected time they'd just blame it on something else, but the problem itself doesn't magically go away.
The graph I found most interesting was:

Instead, a member of the Chinese Politburo harangued them for almost an hour, describing the U.S.-China relationship as a “clash of civilizations” and boasting that China’s government-controlled system was far superior to the “Mediterranean culture” of the West, with its internal divisions and aggressive foreign policy.

Specifically the "Mediterranean culture", which I assume refers to the Romans, and their careening from one leadership extreme to another, civil wars, warmongering, alternating between competence/incompetence and morality/corruption, etc.
Does Clojure lend itself idiomatically to any style other than quick-and-dirty prototyping, though? There are real benefits to many features of Java when it comes to long-term maintainability, even though it also has some very real pitfalls at the same time (no optional values, no variant records with pattern matching, no composition-plus-delegation-over-inheritance etc. etc.).
The issue is not about whether people "favor" the opion of the author or not, it is about whether the article meets the HN guidelines [1].

[1]: https://news.ycombinator.com/newsguidelines.html
People have limited time in their lives. If you want to recruit volunteers to your open source project it has to be in a language they either already know or are interested in learning. It may not be “hard” to learn Clojure, but the potential contributor may consider the time and mental energy spent fumbling around frustrated with all the off-putting sigils and different brackets to be better used learning a language with brighter prospects.
It should, but I doubt it will have any significant impact, unfortunately.

It pays to not give a shit about security to get the product out faster. See e.g. WhatsApp. They had monthly breaches but still got big, and then cleaned up their act.

Had they tried to do it right from the start, a more aggressive and reckless competitor might have eaten their lunch.
The context here is Japan, where houses and buildings are worthless, not America
Those aren't universal rules. I knew a man by the name of Moon Kim, originally from Korea but then a US citizen.

We change name order for the same reason that we change the order of anything else in a sentence. Partial translation creates confusion.
If a useful feature is incompatible with OO, it's a problem with OO, not with the feature. Properties allow one to work with plain old data (not everything is meaningfully an object with behavior) without freezing the underlying implementation forever. Fewer (or maybe more decentralized) religious arguments like this is one of the few things I like about my job in C++. (Shame C++ doesn't have properties, these would come in handy in refactoring config handling code that I currently work on, but on the other hand the last thing C++ needs is yet another feature hidden under common syntax that may blow up allocations and runtime unexpectedly).

EDIT: to clarify: for example, I consider std::optional as an example of a very "un-OO" type that's immensely useful. In general I like the idea from functional programming that complex types can be treated no different than primitives, rather than the OO way of wrapping and uplifting everything until even integers have methods.
Adobe Photoshop & its friends? Microsoft Office? Just a few examples, I'm sure there's plenty more.
Have you had a look at GraalVM? Their native images [1] allow compilation of JVM-based languages into binaries with fast startup behavior and low memory footprint.

[1] https://www.graalvm.org/docs/reference-manual/aot-compilatio...
Great to see mainstream media picking this up and giving Firefox some exposure.

With Microsoft switching to Chromium, Firefox is now the only viable (cross platform) alternative. FF gaining back a solid amount of market share is critical for the browser ecosystem in the future.

(Personally I switched back to FF after the first Quantum release, which brought performance back on par with Chrome. On mobile, the ad blocker is even more essential to get somewhat acceptable load times...)
I hate when people say you never should that in production. A lot times when I am doing something weird it's for fun.
Show HN: Phishing framework built for educational purpose
I dare say it may be because they are more conservative regarding feature adoption.
I've worked somewhere before where there have been flakey tests and they had a system to detect them and list them, and they could be assigned to people. Pretty nice.

I'd like it to exist as a service yes, if it can plug into any testing output, and accurately know that yes something is a flakey test. The telltale sign is a retry on the same branch fails then passes with no source code changes.

I am not sure however if any company I worked for would PAY for such a system. That's a different question. But as a developer I'd like to use one if it is well honed.
Summary: Describes an interactive tool for monitoring and visualizing an automated search for which of several machine learning algorithms might perform best on a particular dataset.
Is there something like that for python?
Thinking a lot about serverless blog and seems this will be helpful. Cloudflare makes many good projects last time.
> The notion of eudaimonia (which is what you talk about)

That's not what's being talked about. Eudaimonia refers to the benefits of living virtuously, a core part of Stoicism, but not the part that's directly being discussed in this article. The ideas discussed in this article are about self-control, disconnecting your emotional well-being from things that are beyond your control, and seeking happiness from within. Those are quintessential Stoic principles. A lot of the modern pop-stoicism also delves into the benefits of virtue, maintaining the connection to eudaimonia and Socrates' question, albeit in a slightly round about way. The only Stoic principle that's usually left out of these discussions is pantheism.

> similar notions pop up all over the place in ancient philosophy

You're right, they do. That doesn't make them any less Stoic though. Perhaps if this was a Chinese message board, we'd all be talking about Buddhism instead. The two philosophies do have a lot in common.