skysight-inc/HackerNews huggingface dataset:
I think you're misinterpreting the statement "For hundreds of years, the best violin players have almost unanimously said they prefer a Stradivari or a Guarneri instrument". While maybe they don't unanimously state it, that does seem to be the prevailing opinion over "hundreds of years". Just because there are violins that match a Stradivarius doesn't change that.

Please audiophiles don't kill me but it seems loosely similar to the debate over lossless FLAC files and a record. Though I will note that unlike the audio debate you're saying there's no perceptible difference between the two.
> See, I'm a "white dude" yet I don't find this statement racist in the slightest.

As a white dude, would you have thought it racist if that line had been modified to read:

"For a Hip-Hop mogul wearing a half-pound of gold chains around his neck, and $400 basketball shoes on his feet, 'the future of cities' might mean zipping around in a flying car while a robot jerks you off and a drone delivers your bottles of Cristal."

Seriously, would you deem that racist or not?
Start with a small praise and how the project had currently helped you. Even just a "Thank you for this awesome tool!" goes a long way.

Do a bit of story telling about why you want this or that. Try to make a good case of it.

Post as most as possible, code, backtrace, steps to reproduce, what did you tried, etc. In a structured way.

Assume you may be wrong. Use words like "Maybe", "We probably should", "I may be misguided, but", etc.

Format it correctly, check for spelling and errors.

Finally, reply back when asked for stuff.

It's not that hard, but most people aren't doing it.
I'm only going off what I've read in these comments (most of which are pretty suspect, to be honest). But it sounds like Ireland have opted to not enforce their own transfer pricing rules by making some kind of special administrative ruling (despite it being inconsistent with the law and previous administrative practice). Truly bizarre, if I've understood the situation correctly.

For starters, it's not like Ireland have a particularly onerous corporate tax rate, so engaging in illegal transfer pricing carries less reward. But, and again I might have the wrong end of the stick here, why in god's name would you undermine the rule of law like that? If there's one thing that governments seem to universally understand, it's that you don't want to do anything to undermine the legitimacy of legal tax collection. It has historically tended to result in either public sector bankruptcy, or revolution...

As for the sovereignty issues, I suspect Ireland (and Luxembourg even more so) are fortunate to be on the inside of the system here. Because the typical response to tax-haven like policies (which suck capital out of other countries and erode their tax bases), tends to be a lot less friendly than being hauled before a EU court.

At any rate, it's just continuing evidence that the EU is an untenable proposition in its current state. Free trade and free movement makes sense on its own. But it's insane to thing you can have a monetary union with any corresponding process of horizontal-fiscal equalisation. Either the monetary union will be dissolved, or EU member countries will have to give up a whole bunch more sovereignty over their national fiscal policy.
How to Learn How to Code
As a big fan of Django, I agree with most of this, but I think one thing that he is missing is the opinionated nature of Django. Its great for probably > 90% of web applications, but there are some use cases where the flexibility of Flask may be a better option.

One example would be the ORM. Its great for easy queries but when you need to do something complex the ORM is lacking (additional conditions on a JOIN for example). If you are going to need a lot of complex queries then maybe Flask / SQLAlchemy is worth the switch.
That's a good point.

But if Frank Sinatra or POTUS wanted to buy up your entire restaurant and force you to invalidate all of the bookings for that evening, you'd accommodate them, right? There is a price you can buy a professional at.
Why not change the relationship?

Find a contributor - on the team or not - working in that area and ask about their rates and what it would take to hire them. Some will not be interested but some will be.

At that point, it's a patch but created by someone active in the project. The worst case is that you can apply it yourself. Not great but immediate problem solved.

Long term, when you go back to the core team, you have a patch that has been tested and used, built by someone in their community, and you're not making a demand but helping address a gap (real or use case specific).

(I've worked on and managed OSS projects for 10+ years and this works pretty consistently. It requires a little more work up front but you end up with a better relationship with the maintainers and a growing network of people who you can contact for specific issues.)
https://news.ycombinator.com/item?id=13227480

https://www.reddit.com/r/sysadmin/comments/5jj3t4/how_skype_...
It should also be very cynically [1] noted that Shami Chakrabarti, the director of Liberty for 12 years and excellent spokesperson, followed Labour party line and abstained [2]. So much for her strongly held beliefs. She wasn't a sell-out though - so she says [3]. No wonder voters are truly cynical about politics.

[1] https://www.theguardian.com/uk/shami-chakrabarti Just look at her history before and after Labour peerage (Aug '16).

[2] http://www.huffingtonpost.co.uk/entry/shami-chakrabarti-has-...

[3] https://www.theguardian.com/uk-news/video/2016/sep/04/shami-...
All I hear from British co-workers is "I don't have anything to hid", "it's ok, I am not doing anything wrong".

:(
Yes, I certainly do think it possible. But it will be more difficult and slower going. Read widely, as the biggest hurdle for a self-learner will be in identifying and filling their gaps of knowledge. Read papers so you learn how to use language such that you are not setting off any crank or dangerous dabbler alarms. Reading lots is also necessary to habituate yourself to the jargon. Read the books by David MacKay and Christopher Bishop. Don't waste time if you're stuck on papers, it means either you're lacking either the shared knowledge or the authors are being purposely obtuse. Save anything you think is the prior for later (unless is a minor iteration of something, which most are). It might take multiple readings spread out over a large time span before you can truly understand the important concepts and papers.

If you can, try and organize or join study groups where the levels of skill are varying. Having a group will help in those times when it seems all too much and you're ready to quit.

Finally, don't try to compete with the well heeled industry titans and their GPU Factory Farms. Find an understudied but important niche where your lack of knowledge is not so much a setback because even if available mental tools will differ, everyone is equally ignorant on the terrain.
> Just my 2p for others learning: for me, Rc::RefCell was what I was missing, even after I thought I was up to speed.

I started (and then stopped) learning Rust a few months ago (before their docs rewrite) and the borrow checker and concepts weren't explain in a way that I could understand. Programs wouldn't work at all, and when I read about Rc::RefCell I was scared because I wasn't sure how much garbage collection rust would do and whether or not it would actually be safe.

So yeah. Rust definitely has problems for beginners.
If I understand the first article about placeholders correctly, concepts are indeed intended to be used where you can use ordinary types, just like traits. That looks really cool, if it ends up in the standard.
I think a lot of art is about charming people with your point of view. A big part of it is moving on from points of view that were charming once, but aren't anymore. A century ago, avant-garde art's point of view was new and exciting, and deserved its time in the sun. But now we know that all those manifestos didn't bear as much fruit as everyone hoped, and the time has come full circle. I don't know what a new and charming point of view could be like, but I'm pretty sure that it won't be like avant-garde art. The OP hopes that it will be more sensory and less theoretical, but more likely it will focus on some other (though related) factor, in a way we can't predict now.
But that is still not "in no way better."
Same with the XPS 13 2017, it doesn't have the power saving nvme mode yet which would I presume give it parity with Windows battery life, and Wayland was janky but X was fine.
If all manufacturers collaborated on a single software project, they could reduce duplicated efforts. That would lower costs for all manufacturers.
After about a year the cat will have pulled the whole thing apart through sheer, continued prying.
> The old way of doing things was to tell kids they are "smart" or "gifted," which resulted in many of those students simply giving up when they failed because smart and gifted are static qualities. So when a smart or gifted child fails, they simply weren't smart or gifted enough. I know many "gifted" students who never amounted to anything because they failed to work at life and simply expected their "gift" to bring them everything.

I was one of these "gifted" children, although the end results weren't exactly the same: when you're told "you're gifted", and things seem easy, you get used to coasting. I was a mediocre college student who didn't even have to try, and made it through college without really studying, but a low GPA. I never had to take a class twice to pass, even the ones that everyone else had to. It used to be, when I would find things challenging, I would get frustrated and give up. I honestly can't remember working hard towards long term goals, and therefore didn't feel very accomplished at much of anything. Most of my motivation was from the pure pleasure of doing things, another area that is oft neglected, to our detriment.

Now, I try to not to get frustrated, to try working things out, especially things I'm not good at, even if I'm not enjoying it at the moment. This is one reason it's important to get outside your comfort zone and push yourself. The focus on not just praising effort, but praising correct effort and offering corrective actions to improve when failure occurs feels very much to me like parts of the deliberate practice method, another area that fascinates me and helps me to try and break complacency.
"Maybe that's how we being to answer the question of what all the truck, taxi and delivery drivers can be doing when those jobs are gone?"

Dunno but I will be stealing the tyres off Auto-Ubers to make my tyre shack/mansion in shanty town.
What about emerging markets? If they are so expensive, they probably don't have access to them.
Low cost, low performance medical devices that target emerging markets seem like a great area to invest massive amount of money into with a realistic chance of generating revenue.

Beware: Just my thoughts, i really don't know much about the market and the money needed. I am probably wrong.
It's true that they didn't impersonate letsencrypt, but they did:

1. Assign DNS records to these two domains and remove them after someone exposed these domains. https://groups.google.com/d/msg/mozilla.dev.security.policy/... https://archive.fo/MQwMK; https://archive.fo/0HQZ7

2. Send marketing e-mails that exaggerate threats of using a "foreign CA", such as Let's Encrypt: https://groups.google.com/d/msg/mozilla.dev.security.policy/... (Well, "Percy" has always been bringing it up.)

While (2) has been something too old to keep bringing up, (1) certainly undermines some of Richard Wang's claim.
Elsewhere in this thread you asserted that "there's a price", and you don't particularly care about cost. Very well: Hire engineers and pay them a market rate.
I think if your lock version is a random hash that is updated each time you write via trigger or app code, then at best someone nefarious could change that value in the form and prevent themselves from being able to update the record.

It also depends on what you're trying to achieve. For instance, if you're just trying to help coordinate people updating a wiki page so that two people don't accidentally clobber each other's updates then it's probably not a huge concern.

From a layering perspective, you can probably implement this with checks and triggers in postgres so that it's mostly transparent to the client.

That said, I wouldn't bother myself ;)
That is disingenuously retarded and trollish.

You seriously can't fathom that knowing financials, track record, ceo, products, pending deals, etc. etc. gives you more information than random chance? How do you make any informed choice about anything at all then?
>It is still my machine, so long as I physically own it. If I run a virtual machine in the cloud it's not mine you see, because then I'm just renting it. If ad networks want to remove the ability to block ads they would have to own the machines and rent out those computers to users, they are free to do this.

You're free to do what you want, but not to read content.
No mention of computers or synthesizers or sequencers or modern music technology of any kind, let alone music of the future.
>It should be possible for all of them. It's not, which is why OSS cannot be relied upon for business.

What's with this entitlement? It really rubs me the wrong way. Don't look a gift horse in the mouth, etc etc.
I very much agree with this.
(My employer pays me to work on a free software project that we depend on.)
Does your weight change between the poles and the equator?
Simpler solution? Place cat feeder on top of refrigerator, long tube to direct falling food down to bowl on floor.
Is this different than cells self-impaling on asbestos fibers because the Si nano-wires are smaller? In the video from TFA it showed some cells with wires going through them that were longer than the cell's diameter.
He did say he had no time to help though, and I think this is a legitimate thing to say.

In my mind, it's similar to walking into a high class restaurant and being told that no, they don't have any tables available for the next three days. If you wanted the reservation for tonight, it was your responsibility to know to book far in advance. You can't decide on your own that you're willing to pay $10k for that table tonight and expect the restaurant to bargain/compromise without any consideration for staff workload, fire hazards imposed by an extra table, restaurant reputation, etc.

The restaurant has the right to refuse service. This doesn't mean it's unfit for business or an unreliable food venue (since you'd certainly be guaranteed a table if you had you made a reservation). It just means your expectations are out of line with reality.
This is a nifty tool that if anything helps the uninitiated visualize how all the parts fit together.

I live in Montreal where conditions for outdoor growing aren't favourable and the grow lights indoors bother me when they're out in the open.

So I'm using the spacebucket approach (with LEDs) to create contained spaces to grow strawberries and cherry tomatoes year round.

Yield isn't spectacular but its fun and trumps anything store bought. I have an upcoming design for microgreens using stacking 2-gal buckets.
I learn something new about rust, eg. irrefutable patterns as function argument in the blog.

PS: I do not understand what irrefutable patterns means, so I google.

https://www.haskell.org/tutorial/patterns.html

in case anyone do not know yet.
NASA Dominated Space and Social Media in 2016
> - Going to sleep, "Hey Alexa turn off the bedroom light. Play white noise. Loop."
> - Wake up in the middle of the night "Hey Alexa what time is it? What time is my first meeting tomorrow? Cancel my alarm for 7:30AM. Set an alarm for 8AM.". All without shining a screen in my face, which can disrupt sleep cycles.

I've seen a bunch of people mention use cases in their bedrooms, which is great, but they seem to fall apart when you're not single since you don't want the speaker waking your partner up, which is sad since I would like to know what time it is without shining a light in my eyes.
That is an argument for private collaboration, not for broad open sourcing.
ADUPS Android Malware Infects Barnes and Noble
Now you are "buying by recipe" rather than "buying by ingredients", which is where the conversation started.
Release Notes for Safari Technology Preview 20
Why can’t they (a) have one process pre-created and ready for me before are press ⌘T or (b) don’t use a separate process to display an empty tab with Top Sites and create a process only after opening it? Or both :-)
This is the fundamental difference between great engineers and the rest. Just giving a damn and being engaged. Seriously.
The main problem I see with this article is the author is totally focused on himself. If you are a solo developer this is fine, but if you are part of a team then his attitude is detrimental.

I work as part of a team and we all work remotely most of the time, but we work the same hours because working different hours would cause problems. It's hard to conduct a daily stand up if everyone's working weird hours. We have some flexibility for people but everybody has to be around for the 9:30 stand up. This helps with coordinating of larger projects and bringing up blockers which the PO or Scrum Master can remove.

If some lone developer is working 3pm to 11pm then that person is not really coordinating with the rest of the team.

Also I'd really hate to hear what this guy thinks of pair programming.
There are the notions of:

o clear written requirements expressing the business and high level technical needs.

o well defined acceptance test procedures to ensure that the delivered software (or hardware or whatever) meets those requirements

o thoughtful partitioning of the work between team members to minimize the needed communication and enable the team members to focus and work on their part without having a committee meeting every few minutes on every minor issue.

None of these are new practices. They, or something similar, is needed to work effectively remotely or for that matter in quiet offices with closed doors.
wat? v8.2 is out and soon in products, v8.3 has been announced. What do you consider to be very complex, if you throw away 32-bit support? What specifically do you consider to be "screwed up", beyond the virt hole with cntfrq_el0, which affects migration between different vendor implementations? The whole VHE affair is more about enabling specific design decisions made by the AArch64 Linux implementation, if that's what you're alluding to. Certainly an ARMv8 implementation without VHE is not broken, virtualization works just fine.
> Or rather, especially assuming they already work hard, they should be motivated to try different approaches (i.e. new techniques for studying or approaching exercises), and ask for help or guidance if they're stuck. Just working harder does not magically solve anything, in fact it may just mean you double down on a wrong/harmful method.

Deliberate practice: it's not just the 10000 hours that make a master, it's the quality of those hours.
it might scare away some users. also some ad providers don't provide proper checking of what content they serve, so if you chose to serve ads, be a bit picky with the ad companies that you can use to do so as malicious scripts comming of your blog will definatly scare people away.... on the other hand, i do support people making a little earning of their blogs, so i don't use ad block, where a lot of people will be indifferent to your decision as their ad block will take care of things.

I would say in the end it doesn't really matter what you pick, though if you think it's a nice little extra at the end of month or year, why not :) little compensation for your efforts / sharing doesn't hurt!

(some pages just slap some adds in the footer or so, so the main content is always displayed first, and the user doesn't have to dodge ads anywhere on the page if they want to click stuff..).
First and foremost, be nice. Secondly, you should assume that anything you "need" will not be built by anyone but you. If you end up with a "showstopper" in OSS, it is time for helpful contributions. Either that or you should find a different solution. A helpful contribution might including opening a civil dialogue about a feature. "Is this a feature that the project could consider within scope? How could I go about adding that feature?" Ask for guidance; don't demand solutions.
I actually enjoy my commuting time. I listen to podcasts or think about what I need to do when I get to work (or home). If I'm on my bicycle, I find that my mine really wanders and I enjoy that.

Once I'm at work, I get down to it and am good for about 4 hours or so (on good days) of really good work. Spend an hour or two on email, light reading, talking to coworkers, and that's my day.
Yeah, putting together the software to generate an image is not lot building a database or webservice. It requires engineering and science knowledge well outside the domain of computer science.
Pretty much. The issue now is, can I implement feature flags faster than I can implement the LaunchDarkly API?

I think I can do feature flags faster.
>I wish GNU people could clean up Savannah and use it as their main distribution point.

Why don't they use GitLab CE? It's under the GPL
No, you can hire programmers to hack on the software. You don't call the authors, wave money at them, and tell them to fix a problem for you.

The programmers you hire don't have to be the authors (that wouldn't scale in most cases anyway), but they may very well become regular contributors.
Japan successfully launches solid fuel rocket
I'm the creator and maintainer of a number of popular open source tools and projects. I even went on to start and build a company around many of them. Prior to that though, I was purely just an OSS maintainer during my free time for 3 or 4 years.

This blog post rings true 100%.

The unfortunate thing is that 99.9% of the community is filled with great, helpful, happy people. But then the 1 in 1000 person comes along that is... less than great... and that person puts a raincloud on your day as a maintainer (or even worse: puts a raincloud on SOMEONE ELSE in the community). And this person usually manifests themself exactly as this blog post states: demanding, lacking detail in requests, not understanding, irrational, rude, etc. They're hard folks to deal with.

I try to remember that THEY are also human. One thing I was taught when I worked at Apple Retail (yes, retail) is that people are angry for a reason. Very very very few people are angry purely to hurt you. Almost everyone who is angry, on the flip side, is angry for a reason and emotions are effecting them. I try to empathize and understand their pain, try to see what I can do to help them. This is certainly a challenge, though. ( See my blog post: http://mitchellh.com/apple-the-key-to-my-success )

Disclaimer for the above paragraph: I'm not saying the blog poster here shouldn't take a month off. They absolutely should if they feel that would help. The constant berating is very mentally straining.

Something that helps greatly: if you're a happy user, if you had a good experience, just open an issue that says "Thanks". Some people close it, some people leave it open. Either way I promise that that little gesture of good will will really help the morale of maintainers. We don't even mind closing your non-issue issue. :)

As a maintainer looking at an issue list, we see just that: a list of issues. Its easy to fall into a trap of thinking everything is terrible and everyone hates what you do. Seeing happy users on Twitter, at conferences, etc. reinforces that its not all pain and despair.

So from a maintainer: thank you to the community for being so great! :)