skysight-inc/HackerNews huggingface dataset:
Like Bill Joy: John Gilmore (first employee) was already on board when Joy joined the Sun team.
Because Brooklyn and Manhattan are nothing like most of the other cities in the US?

Also, what the hell is this author talking about? People are looking at your bike because they think its interesting. It IS interesting, because it looks very different than most bikes people have seen, even people who are "in" to bikes (like bike messengers, that he mentions).

Also this:

>“How do you steer that thing?”

>“With the handlebars”

Oh man you sure showed him, author! The guy outside of the supermarket is clearly showing interest in your unique, interesting bicycle. You don't have to be a jerk about it.

--

People in the US largely don't have the time to ride bikes. We work from 8:00am to 5:00pm, and it's too expensive for many people to live near where their office is. If you pad an hour on each side of that work schedule for commuting, that leaves 13 hours of non-work-related time per day, 8 of which has to be dedicated to sleeping, leaving 5 hours to "live" each day. If you take 30 minutes to get ready in the morning, and 30 minutes to wind down before bed, that brings you down to 4 hours.

People want to reclaim as much time as they can for living. Cars give them the ability to do that. It would be great if we all lived a mile from where we work, and could all ride funky unique bikes to our jobs, then post self-righteous blogs on a website called "bike snob" about how annoyed we are that people notice our weird bike.

But we don't, and blogs like this only serve to further the distance between cyclists and non-cyclists.

On a semi-related note: my city recently got a BUNCH of dockless bike share bikes. They're EVERYWHERE now. Pretty much any bar, any grocery store, any restaurant, shopping center, etc. all have a few bike shares parked outside of them now. It's AWESOME.

And yet every bike-group I'm a part of is complaining about them.

So I don't know cyclists, maybe you should turn that "bike snob" lens towards yourself and ask why more people aren't ditching their cars for bikes.
No, they are not aware that trust is the bedrock layer in a relationship. In the same way that people who verbally or physically abuse their spouses are unaware. They are filled with an all consuming jealousy that makes any violation of privacy seem justifiable to them. These are not people who are thinking rationally or sensibly.
if you're driving the bike mentioned in the article, I bet you aren't averaging 15mph
There's also a good writeup from Asciinema [1] with a similar theme. These are valuable articles from people who have clear domain knowledge in their problem area, which accurately discuss the pros and cons of both approaches.

There's a huge difference between "Go doesn't work for us, here's why, here's what works" and "I don't like Go". The latter should be a Facebook post and has no place on HN.

[1] http://blog.asciinema.org/post/and-now-for-something-complet...
Even more so.

Between

var v T
if (cond0) {
v = value0
} else if (cond1) {
v = value1
} else if (cond2) {
v = value2
} else {
v = default
}

and

val v T = cond0 ? value0
: cond1 ? value1
: cond2 ? value2
: default

I'd much rather have the latter.
And that's fine, I have some Dick Sequerra MET-11's that have been around for many years before I was born and I only had to repair the tweeters two years ago. However these were high quality expensive speakers when they came out. Cheap drivers were not used. Looking at the HomePod and the processing hardware and their margins, there's no way the drivers they are putting in this thing are any better than what you'd find in a cheapo HTIB system.

The way I see it, these speakers are great for somebody that wants to remain in the Apple ecosystem and has $350 to drop on something that's going to be obsolete and incompatible in a few years. So yeah maybe these drivers won't need to be replaced, but that's only because the software driving them has a shorter life expectancy.
They're super common in NL and BE. So I guess the inferred question is why can't they be common in NYC?

From the Article:

> As it happens, as a male cyclist I have indeed experienced that same line of questioning, but only while carrying children on my bike, and only from women who were concerned for their safety.

I would not want to ride a bakfiets in traffic in the US with children riding along. I would be concerned for their safety as well.
Golang wouldn’t be “ported” to a new platform like, say, python. You would need to re-compile for that platform, and address any platform specific code at that point.
In my experience that space is dominated by Wordpress-based websites. Hosting is easiest on wpengine, https://getflywheel.com/ and similar. Ideally you charge a one-off fee for creating the website, then ongoing maintenance fee. The big hosters have bulk-plans for 10+ websites and take care of software updates, backups, caching, CDN etc.

Expect local businesses to be clueless about their wants and needs, especially design, and in general being cheap.

Usual on-top services are SEO consulting, managing social media presence, email hosting.

Good luck!
Does help though, you can get away with way less workouts per week if you cycle every day. Most people barely workout anyway so it would definitely be an improvement.
They’re just being assholes. No seriously - this is all you need to know about their thought processes, because this is all they know about their thought processes.
Okay, "can't" is too strong a word. But I don't know a good word for "it's technically possible but is cumbersome, is not idiomatic, and requires introducing another stack frame for no good reason".
That bike would fit right in in Portland. Would still probably get some comments, but cargo bikes are not uncommon.
We all learn differently, but I found Brave Clojure was a quick read:

https://www.braveclojure.com

From there I just started small by building some command line applications to solve every day needs. Many enjoy solving problems at http://www.4clojure.com as a method of learning.

Perhaps one of the main differences for someone coming from an OO world is that in OO, to learn an SDK means learning about all the classes and the methods they expose to operate on encapsulated data. You're limited to what you can do on the data via those public methods.

In a functional language, you instead learn a large amount of functions that operate on raw data directly. Then you build your app by creating functions that take an input and transforming it into a new output using these common set of functions.

One of the exciting things for me is Clojure Spec. One of the recurring problems in web development in an OO app is that you have some domain class like User and you have some service function which does CRUD on that User.

// Look how great our model layer is!
createUser(User)

Then as the app grows you have another service function which takes a Order object and 80% of the properties of User.

So you may start with this:

// uses 100% of order, 80% of user
doSomething(Order order, User user)

Then you have another service function which takes 3 object but only uses a few properties of each:

// this feels like a code smell
doAnotherThing(Order order, User user, SomethineElse somethingElse)

If you have a large team without a strong common practice an application can quickly turn into a ball of spaghetti:

// let's list out specifically what this function takes
doAnotherThing2(long orderId, double orderTotal, long userId, String userName, A something1, B something2)

And then you reach some maximum amount of parameters and refactor it to this:

doAnotherThing3(DoAnotherThingRequest request)

DoAnotherThingRequest feels right but it's redefining the types of all of the properties already defined in our domain model:

class DoAnotherThingRequest {
long orderId;
double orderTotal; ... }

And then you have another function which needs DoAnotherThingRequest and a few properties of another class:

class YetAnotherThingRequest extends DoAnotherThingRequest {
A something; ... }

And eventually you realize this is stupid and instead you do this:

// Let's just use the raw JSON!
doAnotherThing4(JSON json)

Clojure Spec on the other hand makes much more sense to me. You can define specs on namespaced keywords:

:order/total is an integer
:user/userName is a string with a maximum length of 10

And then your function can specify the shape of the data they receive:

; this requires an order total and a userName (Note: it doesn't redefine their specifications)
(s/def ::do-another-thing-request (s/keys :req [:order/total :user/userName ...])))

This makes much more sense to me as a way of building large systems. And then you find out that Clojure spec can generate tests on your functions automatically based on the specifications you created and your mind is blown. :)
Unlike typical assembly, WASM enforces strong guarantees around memory safety (which I'll argue is precisely what you want for something with a web browser's attack surface). This does imply a performance hit (conventional wisdom is that WASM will, at best, be half as fast as "native" code), but also insulates the user from the usual memory-related pitfalls of C. Code transpiled from Rust is forced to pay this price as well, despite Rust providing substantially stronger memory safety guarantees than C; fortunately if you're using Rust you'll probably be the sort of person who agrees that this is a good thing, because Rust still lets one drop into unsafe blocks and potential memory unsafety in untrusted code delivered over the network is pretty much a nightmare scenario.
You should get the iOS app: https://itunes.apple.com/us/app/instant-domain-search/id1068...

It uses the streaming API, and will work well for you.
On the topic of Google finding issues in others' software:

I am wondering how do the engineers at Google that work on finding software issues or vulnerabilities approach that kind of work? Is there a way to heuristically find security vulnerabilities and software issues?

Edit: Especially when those vulnerabilities need so much work to be revealed, like the meltdown/spectre issues we heard about recently
There’s a Persistent Hum in This Canadian City, and No One Knows Why
I've had drivers intentionally swerve into me because I'm an "asshole" for taking up some of the right side of the lane. A lot of people are jerks to bicyclists. Even had a guy yell, "pay registration like the rest of us." To which I yelled back, "I do!"

In LA it was common to give extra room to lane splitting motorcyclists, and they'd give you a wave to show their appreciation. Rarely do I ever experience the kind of courtesy afforded to motorcyclists I observed while living in LA as to bicyclists in the city I live now. I did have a gentleman with a bike rack on his car move over for me while stopped at a light to give me some room, but of course, he understood as a fellow cyclist.

My out-there suggestion is to force any able bodied citizen to ride a bicycle on the road prior to getting a drivers license so they at least know what it's like.

Or best of all, cities should model their bicycle infrastructure like Portland, as I can't even recall an incident between myself and a vehicle while living there because of how they designed and implemented bike lanes.
Indianapolis has a very similar relocation story from 1930, with the 11,000-ton Indiana Bell building [1].

Fun fact: Kurt Vonnegut's father was the chief architect who recommended rotating the building [2]. Earlier than that, there was also a building that was moved by a team of horses to make way for the Indiana War Memorial, but I can't find a source anywhere (I read about it while touring the memorial).

[1] http://www.paul-f.com/ibmove.html
[2] https://www.indystar.com/story/news/history/retroindy/2014/0...
I found it to be self deprecating, in a humorous way.
Bears burned in Thomas fire sent back into the wild after rehab
When I biked to work, I lived close to the downtown of a mid-sized city in the US - with traffic, I often wound up getting to work faster via bike than car.
Few if any CEOs employ any fetuses, so there is little chance that they could create a hostile work (which they are legally required not to do) for any employees by opposing fetal rights. The same can not be said for a CEO who opposes LGBTQ rights.
> Excessive democracy leading to indecision

This is one I've hit a number of times, my solution in the past has been to 'go rogue' and get something done, people will be bothered (usually someone unofficially says it's a good idea), if it works out often enough, we'll start 'deciding' to do more things if for no other reason than to take some credit.

While reading, I was trying to come up with a cohesive idea as to why these things happen, or what single thing could prevent them. The best I could come up with is having a good 'Director of Development' or maybe Project Lead. I don't know what the title should be because I haven't really worked for one. I've worked with great team leads and companies with fine CEOs. CTO's are rarely close enough to the problems being solved and often just not available. I myself worked as a Director of Development for a small startup that eventually ran out of runway. The dev's said they enjoyed working together but I don't think it was long enough or going through the many pivots to test out how that would have been.

Most places I've been have business people that plan projects. Then there are product owners and PMs with teams, design/UX, front-end, back-end, SRE/devops, sometimes even multiple teams with overlapping roles to execute. This I know, doesn't work for long.

Startups that grow and promote internally to fill such a role, may or may not work--depends on the individual. What's really needed is good alignment and balance of business goals and employee happiness. Two things which are both true: startups need to iterate fast to find that magic point; employees are a company's greatest asset. You can't forsake one for the other.
I have had a phone book thrown at me (among other things) while cycling and this is in California, USA.

Lot of angry people live in this country; when they are driving cars it really comes out.
As someone who audit code for a living, yes it is bad oO that would be a nightmare to go through
Ask HN: Are Facebook-driven sales incompatible with GDPR?
As far as I know, the only "official" way of tracking Facebook sales is their "pixel". Unfortunately, Facebook has a habit of using the data collected by those JS snippets for its own profit. If I understand it right, every single Facebook ad client under GDPR must provide:

- an explicit opt-in for any tracking, including Facebook's (so the pixel can't be included on a page until user gives their consent)

- the opt-in message must be clear that the data will not only be used by the business, but also by Facebook for… what exactly? (looks like it's impossible to even state that message because Facebook doesn't tell anyone how they use user data)

- user must be able to cancel that opt-in and all their data must be removed. It's impossible to initiate that process being Facebook's ad client

I wasn't able to find a single word from Facebook on this issue. Starting this spring it becomes illegal to use Facebook to track ads. Has Facebook really left its EU customers hanging?
Never had anything thrown at me, but I have been close passed and sworn at more times than I would like to count.
Most people in the US get little or no exercise. __Any__ exercise would be a big improvement over none.
I have no idea why there is so much misunderstanding on this thread. Deodorant is NOT just fragrance, it is primarily an antibacterial. It is literally preventing odor. I do not understand why this is so difficult to believe.
Apple has been so perfectly gentle with the Chinese government that their phones were allowed to show up in this year's CNY broadcasts.
This is absolutely not a "fact of life" in the USA. At various points in my life, I have spent a lot of time riding my bike on the streets. I have never had anybody throw anything at me.

Although this is probably because I am courteous and acknowledge that my bike going 15 mph is essentially an obstacle to all of the cars which are going 45 mph.
There are many more people being productive in Not Go than there are in Go. Taking this argument to the logical conclusion, we should all be using... what, C++ or Java?
That's the problem though. It doesn't matter much that it's open source if it is not usable in a sense that you can't easily deploy it yourself or repurpose, without committing (and paying) for the rest of Azure stack.
I'd call it descriptive. I cite it because I like The Atlantic and because I think it's one of the more balanced articles on the subject.

It covers both sides of the story, including people who seem to be celebrating.
In its heyday? Java is still scads more popular than Go.
Power series and power law distributions are completely different things
That's not relevant. Low / high estimates can be written in this form: X hours +/- Y%. 1-3 days seems wide but it's just 2 +/- 50%. 1 hour or 2 days ~= 1 day 1 hour +/- 90%.

AKA Y is much higher when you deal with low hour estimates.

This is most noticeable when you have lot's of tasks. If you think 200 tiny tasks may take 1 month or just over 1 year that's an almost useless estimate.
Dart came way, way later. And it was a new language, while they could have just used an existing one. They could have implemented lua, ruby, Python, anything with a good track record. With the millions spent on V8 with those geniuses working on it, can you imagine how fast one of those language would have become ? The tooling it would have had ?
Also Sanctuary RPG:

http://www.sanctuaryrpg.com/

Unfortunately, they only run on Windows, not Linux. They are missing out on a large audience that likes text-based things.
Those who put resources into looking for security vulnerabilities find a lot. Of those groups, most have better things to do with those vulnerabilities than report them publicly. Who else is Google even competing against here?
http://jsonlines.org/

> Each Line is a Valid JSON Value

This seems like the better option I agree.
WeakNet 8 CAFFEINE a Linux distribution designed for network penetration testing
The problem with capitalization for me comes when interfacing with external json. Suddenly serializable structs have to be exported (since introspection doesn't work on private structs) which means that none of the names match the json names anymore (the web world tends to use lowercase or camel case with the first word uncapitalized). So now every json structure had to not only be public but also has to have introspection hints (`json: "my_field_name"`). It makes everything verbose and ugly. In these cases I'd much rather have "pub" in front of some lowercase names that match the json I'm reading or writing.
Turning big data into sound
https://github.com/plexus/chestnut is Clojurescript, but it's fantastic. It's quite easy to roll out a UI and you can build your backend to your specifications. A bit less opinionated than Luminus, but both great for just getting started.
I will be sarcastic, ironic and voluntarily provocative: he is an idiot, if he was a real 10x developer, he should have chosen a complex code architecture only understood by him, that way he would have been the only one able to implement and maintain features inside the code base, making all the other developers 0.1x and consequently he would have become a 10x developer himself.

More seriously, this kind of situation can happen without ill intent, simply have a fast developer with a strong personality and he will become the lead for everything and the only one able to understand the code base.

Also the velocity of an individual developer can be overvalued and mistaken for a 10x, it's certainly easier and faster to write spaghetti code instead of a well designed/architectured code base, but doing so can have dramatic effects down the line, or even immediately for the other developers in the team. Yet it can be a quality in critical situation (like our startup will shutdown if feature X is not implemented in 2 days).

It can be hard to differentiate between a developer like I describe and a real 10x developer you describe. The applications we designed can be quite difficult to implement depending on the complexity of the domain specific logic the application deals with. Sometimes it's impossible to recognize between complexity caused by the application architecture (generally avoidable) or complexity inherited by the overall domain logic (nearly unavoidable).

And lastly, it's never, ever as black and white as I describe.

That being said, your colleague seems like a really good developer, able to see the big picture and steer a code base in the right direction. I hope for you that he will part of your team for a very long time.
Last time I tried streaming parsing it was with Oboe.js which wasn't bad but I remember it having approximately a 5x speed penalty. So you get your first item in your dataset faster, but the whole thing loads slower - a tradeoff that's not a no-brainer. I wonder how getline plus many repeated calls to json.parse work in comparison to that - I suspect the native parser probably has some startup overhead but still better than a JS parser.

The other thing was that to get the full benefits of something like this (not necessarily about streaming parsers vs not) you had to rearrange the way your /whole/ stack works, streaming all the way from the database through all the backend layers to the frontend. It's satisfying when it works, but definitely a non-trivial amount of change.
I've been riding a bike to work on and off for several years, and I pretty much also think cyclists don't belong on the road. The road is dangerous, far better to ride on sidewalks.

In the Northern Virginia suburbs where I live, there aren't a lot of people on the sidewalks. When I do pass a pedestrian, I slow down and give them a wide berth so they aren't startled. Sometimes I'll even ride into the street to give them more room, especially if they're walking a dog. And then, I get back on the sidewalk where my life isn't in the hands of aggressive or distracted drivers.
> If googles approach is to force people fix them, so be it.

That's not actually what responsible disclosure is for. Responsible disclosure is a process that [correctly] assumes that a malicious third party has also discovered the bug and is currently exploiting it or selling it, but acknowledges the assumption. If you disclosed bugs immediately, the could be novel and you could have let the cat out of the bag. If you never disclose bugs, they could already be in the wild and doing damage.

Forcing Microsoft to fix it is just a beneficial side-effect.
Ask HN: Can .NET win back developers?
I'm employed as a .NET developer, but I have typically avoided .NET for personal/side projects in favor of open source tech stacks. I think most of us can agree that under Steve Ballmer's lead, Microsoft did a lot of damage to the .NET ecosystem with the stack being proprietary, full of vendor lock-in, not cross-platform, etc. But all of that is changing under Satya Nadella's leadership. Is it winning back developers?

.NET Core is now free, open-source, runs on MacOS, Linux, and Windows, and as of December 2017, includes ASP.NET Core which supports Nginx, Apache, Docker, in addition to IIS.

C# as a programming language is quite good (subjective, obviously). The .NET library is also very extensive - it had to be, since few developers were willing to build free/open-source libraries for a proprietary framework.

That being said, .NET still gives a lot of us a bad taste in our mouths, and I still don't see much mention of .NET anywhere on Hacker News. Is there any evidence that Microsoft's efforts are pushing the needle on developer sentiment?