skysight-inc/HackerNews huggingface dataset:
I agree that automatically carrying over todo's to the next day is a bad idea. You need to be able to trust your todo tracker. It would be helpful to have some sort of history/log of your tasks just in case you need it.

It reminds me of https://complice.co/ each day you need to put in your new tasks but you get to review yesterday's incomplete items and pull them in. It has a lot of smarts built in and tell you you've pulled in the same task day after day and suggests you split it into smaller pieces.

Nice job shipping aswinmohanme!
Crops are not capable of suffering. Another publication that spreads the idea that inanimate things can suffer, while the true suffering is experienced by workers.
Should wait to see if data was compromised, they can fixed the extension though.
Mozilla Project Things
I agree that HTML/CSS is easier to use, though maybe some of that is just because everybody has been using them for years. However, you certainly don't have to override ::paint() to get rich text inside a label. You can use a simple subset of HTML in your QLabel to get various text effects.
When I saw this a little while ago I thought it would be great for automated video analysis of barbell lifts / weightlifting given the angles involved in such things can be a good metric for form.

However, the license specifically states that you cannot use it for sports. I wonder if they singed a high value exclusivity agreement with someone in that space, or if some such company funded the research originally...

"The non-exclusive commercial license cannot be used in the field of Sports. ("Sports" shall mean any and all athletic competition between individuals, groups of individuals or teams.)"
async/await means you mark all your yield points explicitly; rather than having the runtime implicitly preempt you whenever it chooses, you mark the points at which task switching can happen, and at every other point it's impossible (equivalently it's as though any block of code that doesn't contain an "await" were a critical section). The syntax strikes a nice balance, making these markers as lightweight as possible but no lighter: you don't want the yield points to be completely invisible, but you don't want them to distract too much from reading through the straight-through happy-path control flow.

I find that having one implicit, pervasive, uncontrolled effect in a given piece of code is ok, but having multiple uncontrolled effects is very much not ok, because the ways those effects will interact can be very surprising. E.g. https://glyph.twistedmatrix.com/2014/02/unyielding.html gives an argument for using explicit async/await rather than go-style implicit (green) threads, in terms of how task switching will interact with state mutation. You can make similar arguments in terms of how task switching interacts with error handling or logging or database transactions or... - one uncontrolled effect is fine, multiple uncontrolled effects cause chaos when they interact. Unfortunately the kind of examples where one can see multiple effects in a single application tend to be quite big by their very nature (and if your app is small enough to only need to have one kind of effect, then using a language in which that particular effect is uncontrolled is probably fine, perhaps even a good idea).
If it is so trivial, what is the big deal with "Single Page Applications"? Seems like plenty of pain there in the HTML and CSS world..

Meanwhile, there have never been anything but Single Page Applications in the native world.

And sure, Qt is now more than 20 years old, it's from a time strongly rooted in "widget" based UI systems that have somewhat fallen out of favor. That is what QML is for, which similarly to WPF that started this trend, allows for GPU accelerated vector composition of anything you could ever want, with sane provided defaults so not every project is reinventing grids.
I agree that drivers have a larger impact for breaking that law than cyclists simply due to the far larger number of them. The size and speed differences matter too.

As far as I'm an tell about the same fraction of drivers and cyclists break the law. They, however, tend to break different laws: rolling through stop signs is more common for cyclists, whereas speeding is more common for drivers. Often when I point this out a driver decides to defend speeding, which I think is the wrong response. If the problem they claim to have is respect for the rules of the road, then justifying speeding is hypocritical. (For what it's worth I follow the law to the letter.)

Plus, as you've said, the actions of a few bad people in a group should not strongly color perceptions of the entire group.
I also recently moved away (I wonder if we know one another), in the last 18 months , and was blown away by everyone's collective delusions about Amazon. With the police terrorizing most communities, the lack of heat in the schools, and the delay in bike plan implementation to 2020+, I can't believe anyone thought it was even a remote possibility.
Browsers should just provide controlled access to the operating system file system which will remove some large percentage of the use cases for Electron. It would be easier and much safer.
I don't entirely disagree but I also suspect that many Americans would be shocked by the cost of food if workers were paid higher wages (especially if it was done for everyone who touches your food as it travels from the farm to the table) and that most farmers would prefer a phased approach to reform so that crops aren't rotting in the fields.
Are you aware of QML, which is part of the Qt framework? https://en.m.wikipedia.org/wiki/QML
Scala and Implicit Implications: Parameters
Hard to imagine it's anything else, but I'd be curious to read alternative suggestions.
Probably, in the sense that there would be fewer operating farms.
Volatility ETN crashes 80%
One place you can see this in action is that [ ] are lists and [| |] are arrays.

JS favors arrays, OCaml lists, so you either write dsls with [| |] (ugly), or you import a module and convert from lists to arrays and your bundle size goes up 80 KB (don't recall if minified or not).

I was surprised to see Reason continue with this syntax. The idiomatic approach for either side is suboptimal unless I'm missing something.
>an ocean that is not capable of supporting the bio mass we rely on for food.

Honest question, does this just apply to people that eat seafood? For instance, if I have never eaten seafood, is my own personal food source at risk? Of course I should be concerned for people that do rely on seafood, but does the health of the oceans affect the growing of wheat, sugar, beef cattle, Doritos spices, etc.?
Please read in between lines... I could easy write any other example. Don't make me compare HTML/CSS's flexibility with Qt's...
One thing I’ll add on top of the other comments is that the Reason community has been trying hard to build tools and libraries for people who are building products. Doing that for two reasons:
1) Most of Reason contributors are actually working on a product, and contribute to Reason on the side (20% or personal time kinda thing)
2) Product driven dev allows us to build simpler things that solve real problems that people have :)
This means that the Reason tools are less powerful but also simpler. In particular I’m thinking of bsb (https://bucklescript.github.io/docs/en/build-overview.html#d...) and bsb-native (https://github.com/bsansouci/bsb-native), the latter’s a simple fork of the former that adds support for building to native. Bsb is simple and thanks to that very fast and easy to setup.
This has been going on for decades, across the country. See also the Rampart Scandal [0] and the Allen v. City of Oakland [1] case in which cops in LA and Oakland respectively, robbed, beat kidnapped and otherwise victimized citizens. I hate to think what happens in small cities and towns where this stuff is even harder to report.

0: https://en.wikipedia.org/wiki/Rampart_scandal
1: https://en.wikipedia.org/wiki/Allen_v._City_of_Oakland
Would it be possible to resolve Electron's performance issues by "precompiling"/prerendering the HTML and CSS (+ maybe scripts) ?
As long as the app UI stays the same, it should be cached in an optimized form.
(sorry if that already exists in Electron)
Taxi and Limo drivers were setting themselves up for such disruption for quite some time. Forget the cost of the ride, if only they (as in, all drivers) had provided respectful and quality service without denying rides or throwing a tantrum for those who chose to pay by card, Uber and Lyft wouldn't have benefited from such anti-incumbency sentiment.

During the pre Uber/Lyft days, a driver himself told me how he worked: Basically, give enough rides till he get's his next meal's money or a bit more. Thats the kind of job security they had. Of course, they were benefiting from the regulatory bubble before Uber and Lyft deflated it instead of popping it.

I feel bad for those who joined the taxi industry just before Uber/Lyft juggernaut started, and were probably singed the worst.But I guess such things happen for those who join industries that are about to be disrupted..

The incumbent Taxi and Limo drivers didn't realize that with Uber and Lyft, they (cab drivers) had lesser political clout, to get favorable terms in regulations.
Show HN: E-commerce conversion and revenue game on with gamification pop-ups
the actual bug is this,

if you play podcast while driving and meanwhile, the alarm is triggered. After you have dismissed the alarm, the audio won't come back. I suspect this is unrelated to my car, to be honest. As I disconnected my phone from the car, the issue was still there, no podcast audio.
I kind of doubt the conservatives will come for them. They're often allies, even if they don't like to admit being friends with unions. The only evil the current Republican party seems interested in banishing from the world is Democrats.
Oh there it is http://doyouneedablockchain.com/
C appears easy to learn. C++ a bit harder, but learnable.

What isn't easy to learn is all the horrible ways C is broken. Don't return addresses to local variables. Remember realloc can change the location pointer. Don't use the C string functions.

C++ adds fun gotchas like using the c_str() of a temporary string object. Carelessly passing local objects by reference to a lambda thread function. All of the amusingly horrible ways to screw up data structures using shared_ptr and enable_shared_from_this.

Better yet, linking C or C++ objects together that have been compiled with different "#defines" set so the structs, objects and vtables are different sizes.

C is not easy to learn.
What kind of argument is this? Any policy that doesn't completely destroy America is good policy?
Or an episode of The Wire.
Another fun one is radix sort[1]. We used to use it for sorting alpha'd quads(think particle systems/ui/etc) from front-to-back. Easily annihilates anything else in terms of raw performance for datasets < 10,000 with int/f32 keys and it's stable(!) for identical values.

This talk[2] from Herb Sutter(starting at 22:30) is one of my favorite talks and does a great job of explaining why this is so important(and why dense arrays are still king in many areas).

[1] http://stereopsis.com/radix.html

[2] https://channel9.msdn.com/Events/Build/2014/2-661
So let's hurt our own citizens for the benefit of other nationalities who are willing to demonstrate their disrespect for our laws, for the benefit of greedy business owners?
100% use of nearly anything is over use, not just because of peaks in load, but because it must both be done and perfect.

Think of a bookcase. 100% means you can never add more books, and it also makes it very difficult to reorganize anything.
> The conservatives will come for them at some point too...

I really really doubt that. All the conservatives I know love the police and think they can do no wrong.
its likely that its completely unusable off the machine thats running it and that there the author can't run it a month later (like grad student work)

I guess you could argue that devoted interested parties would invest the time to tease out all the dependencies, get it integrated in common packaging systems, and spend some time debugging it.

if you had an even slightly more devoted person they could make a production system using the demo as an inspiration. I don't know Bret personally, but he'd probably be likely to engage with that person and give feedback and advice.
This seems easily resolvable via a DMCA infringement claim, but there’s no mention of one in the article. Perhaps the copyright owner (i.e. Kempf or his agent) didn’t file one? The process is pretty straightforward.
Suffer, intransitive verb, definition 2: to sustain loss or damage.

(https://www.merriam-webster.com/dictionary/suffer)
Fine, but no one is suggesting that motorists not use the infrastructure that they are legally entitled to use which is the case for cyclists(not you, specifically). I'm sorry this has gotten so wildly off topic and if anyone would like to continue this discussion they are welcome to private message me- or do it here, but I won't be responding!
At a previous job we practiced aggressive, automated ticket de-prioritization. Every N days of inactivity, a ticket would drop one priority point (and I think higher priority tickets were de-prioritized at a higher rate). The theory was that anything that was truly high priority would have been done. In other words, things that we left on the queue were actually lower priority than marked. Given our extremely limited developer-hours, it was important to stay focused on the things that actually mattered.
Consider title insurance [1].
The current system of land registry in the U.S. is so disjointed that you need insurance against the registry making mistakes.
This might be solved by making a centralized database, but then we are depending on the technical capabilities and security of the court system.
Just because we trust the court to make correct decisions does not mean we trust the court to keep that data correctly and publicly available.

Besides, a system like this could allow for land transfers that are recorded only in the blockchain, without need of an intermediary.

A harder objection would be complicated deeds. For example, a deed that grants a piece of land but requires that, when it is sold, the proceeds go to some charity.
For cases like that, you'd require a signature by a trusted third party (an oracle).
We are now trusting that oracle only to make the right decision when the signature is requested.
Moreover, it is now public data that there is a complex deed behind this transaction.
Thus it is no longer possible that upon sale, the deed has been forgotten and then later it turns up wreaks retroactive havoc.

Another issue would be 'property loss'.
People lose their crypto keys all the time, what happens when people lose the 'key' to their land?

[1] https://en.wikipedia.org/wiki/Title_insurance
SERVICE OPTIMIZER: HIRE FREELANCERS, EXPERTS, AND CONSULTANTS AT EASE (B2B)
Yep, came here to say that. QML is absolutely great for making UIs, in fact I wish we could use it for the web, too.
The inner harbor area seems safe enough and has interesting tourist sites including several museum ships.
As a hypothetical this an interesting question, for me at least, but you're a bit too vague.

Obviously your talking about development, coding, but what's your area? Back-end? Front-end? Mobile? Desktop? Server? Which OS are you targeting? Macs? Windows? Linux?

Then of course, what's the number? How much do you need/want?

A vague answer for a vague question: Build something in an area you're familiar with that addresses a pain point you have or people in your network have, make them your first "customer", give it to them for "free" in return for feedback.

Another: Build something for a niche, spend a couple days researching your chosen niche and find a small-moderate sized community that you can easily (quickly) immerse yourself in. Be honest about your intentions.

More importantly though, adjust your expectations. Realistically there's not a single thing (that I can currently think of, off the top of my head) that you can build in a week that you can sell "for years to come" without work, if you're looking for a passive income the answer is real estate.

Technology moves fast, updates will be required. Maintenance will be required. Development is mostly an iterative process. Users will request features. Features will introduce bugs and so on and so fourth.

Also what do you mean by bootstraping a business? You can be a registered business entity within a couple hours. Which means shit if you don't have a product/plan.

Good luck :)
I pedantic point, but I think crops probably qualify as animate.
With public records, a big question is whether you need some form of distributed Sybil resistant consensus.
You don't scale. If you find a way to make sites more accessible, can you modify all existing sites that you've made? If you find a way to make your sites load 10% faster, can you deploy that to every existing site you've already made?

Also, how many sites can you make per day? If you could make 100x as many sites, you'd learn more about all the weird things that customers want. With machine-generated sites, you could then apply those lessons to all new and potentially old sites.
Increased labor costs provide an incentive to reduce labor costs. When labor costs are higher than automation costs, there's an incentive to automate.

If you consider the existence of human labor undesirable then automation is always good.

If you consider jobs the end-goal of human existence then automation is always bad.

In all likelihood you're somewhere in between those, and whether automation is good or not depends on external factors. GP seems to lean more towards the "human labor is bad" side.
It is just the hn title that is terrible. The article has the following title "California Crops Rot as Immigration Crackdown Creates Farmworker Shortage".

Somehow the hn title manages to put the blame with the Mexicans.
Camden shut down it's police department, and last year had the lowest murder rate in decades: http://www.nj.com/camden/index.ssf/2018/01/camdens_2017_murd.... As engineers when a system is severaly broken, we know the answer can be to turn it off (e.g. in the case of a bad malware infection). The same can apply to other complex systems too.
Given the state of text tools do you think it would it be viable to pipe a Readability Redux scrape into Aframe?
I agree... and I think there is a similar POV when looking at the results of tkinter and an Electron app. The visuals alone are worth it... let alone the ease of development and packaging.
Been here for almost 4 and agree about the affordability aspect.
You could buy a rowhome less than 3 miles from O's stadium for like 250k in a not-terrible neighborhood.
Yes old PCs can be unusable too, but I can still use desktop PCs released in the same era as the first smartphones, and with upgraded graphics, memory and SSD they last even longer.

As a counter point I recently got a 12 year old MacPro to fix up and it is almost impossible to make usable even though the specs are better than some old PCs I've given away. So it's an design issue and Apple is a real crook in this regard.
I just switched from VS Code to InteliJ and it's great. There's been huge improvements in IDE support recently.
Israeli Students Spoof Waze App with Fake Traffic Jam [2014]
You don't have your own personal food source. Everything is connected.
Some of the same applications are also cross-targeting mobile with Cordova, and/or are already or are working to become PWAs.
Do you have data to support this claim? What proportion get paid leave vs. fired (or jailed)
To add to what Kevin said. We depend on hardware support from the different vendors. On the high end Oculus is Windows only and SteamVR is still experimental on Linux and Mac. OpenXR (https://www.khronos.org/openxr), the upcoming standard to interface with VR/AR hardware will make it easier for browsers to integrate new devices.
They don't need to be public. A $5 RasPi Zero would be plenty powerful enough to serve photos on a local network.
I'd add to that "not obfuscated" too since JS minimization and WASM can be as obscure as binary.
Oh wow. The screenshot with the large text the guy says "Google's free products shouldn't be used for business." Yikes.
As a web developer, setAttribute('data-gramm', 'false') is your friend.

For better or for worse, between browser extensions loaded by the end user, and "tags" injected by your well-meaning business analytics team - see my comment here: https://news.ycombinator.com/item?id=16314501 ), the extension ecosystem has become the new Internet Explorer in terms of compatibility testing. Luckily most of the workarounds are trivial, but it's essential to have good QA on actual client machines if you're doing, well, anything at all.
Is Apple Music really about to pass Spotify? The data doesn't back that up
what about the converse of this? what about producing a basic set of content and letting AI taxonomise or organise it and then create a design based on design models. It could work both ways. I guess ultimately the problem will be solved both ways and AI could create entire experiences based on specific domains. Also, for those claiming this will never work i would suggest looking at some of the amazing stuff being done with AI right now. This kind of problem, including optimising and making best usage of html/css is almost tailor made for AI.
This article would justify a submission of its own but is so spot-on in reply to your comment; here we go:

https://www.newyorker.com/magazine/2011/02/07/crush-point
If only there were some sort of market mechanism that would incentivize legal US citizens to perform these jobs, in order to spare these suffering crops.
Take care of yourself.
That doesn't square with my experience. I've taught beginning programmers more or less the "C subset" of C++, and it was a nightmare.

The biggest problem is that when they inevitably hit undefined behavior, there is no easy way to learn what is wrong. The program hits a segfault or prints garbage on the screen—where to begin? I instinctively know what is likely to be wrong, but that's only through years of experience; it's almost impossible to teach that quickly. Even if, by luck, the program segfaults instead of silently corrupting memory, the line number where the failure occurred doesn't necessarily correspond to what is wrong—often the problem occurred earlier.

Rust is in a much better position here, since the compiler can actually isolate precisely what is wrong in those cases and emit diagnostics at the exact location where the problem occurred. That's much easier to teach.
Totally. Here's some more info on the company. They are located in the Ukraine. http://escadra.com.ua/en/kak-dvoe-kievlyan-sozdali-servis-pr...
This seems like a super-interesting discussion but I can't quite follow due to the mixed-up naming. Is there a good paper or website that clarifies what stackful/less means in the various contexts?