skysight-inc/HackerNews huggingface dataset:
If haskell is that much harder, it should benefit from better tooling that much more. I think there really is a big difference in the priorities. I've never played around with GHC, so I have no idea how hard tooling is, but I know some good old humans are at least able to contribute (https://izbicki.me/blog/error-messages-in-ghc-vs-g%2B%2B.htm...).

edit: It looks like the error message changes may have been reverted (https://phabricator.haskell.org/rGHC92c924e07dfef327509555c2...) :( Sad that they reverted it instead of fixed it.
We had sourceforge, google code and several similar places long before github. Github pounced on the opportunity that git opened up because other hosts were slow to adapt.

So yes, without git there would be no gihub as we know it.
> Why Are America's Most Innovative Companies Still Stuck in 1950s Suburbia?

> Stuck

This already implies a negative connotation of "1950s suburbia". Like we ought to move on, just cause.

What about the flip-side of this question: what is it about a 1950s suburbia that helps America's Most Innovative Companies? I'll offer some ideas. Maybe it's a lot more stable socially, so there's most local community trust and engagement, and more mental energy to devote to one's work. Families are stable and know and support each other, e.g. community caregiving responsibilities for children. As well, there's less distracting "events" going on than in a typical city. And so more mental thought and energy can go into work.

As well, it's cheaper to not be in a crammed urban center. This also helps play into a certain level of "mental safety" if you will that enables one to focus more on their work - what else are you gonna focus on?
A tiny house might be liveable in mild/warm climates. I live in a cold country and spend most of my time indoors. Couldn't imagine being stuck in a tiny space all the time I home.
I concur. The silencing of opposing viewpoints, even if they are utterly distasteful is getting out of hand. Sure, we are entitled to disagree, and the law may prosecute when appropriate, but this mob mentality is very dangerous for democracy. I too find it ironic that the so called left is tolerant, but only to the degree that you agree lock stock and barrel with the party line. Of course, in this case many people (on the left and right) despise Trump, but we can despise him without acting to suppress the free speech rights of those who support him. The argument I'm hearing is that if it's individuals and businesses severing ties and punishing the opposition for their positions then it is okay. Apparently it's okay as long as it's not the government diminishing the free speech right. The problem is that the right to free speech is infringed in both cases. In order to get the American people back on the same page, to resolve the growing polarization of our country, we need to have MORE respect for opposing viewpoints rather than less. I suppose the main issue I have is with corporate entities (which are supposed to exist separate from their owners and stakeholders as apolitical identities) when they are wielded as weapons against those who express distasteful or unpopular opinions. Individuals can express freely their disagreement, but the making businesses and organizations political beasts is exceptionally dangerous to this country's future.

To me the attack on Peter Thiel amounts to a wholesale attack on free speech.
Oh you're right. https://github.com/petkaantonov/bluebird/blob/master/src/pro...
Thank you for looking into the details.
Looks like something is working, the browser is receiving an image and it's not a solid black colour, turning up the contrast to the max you can see some difference:

http://i.imgur.com/Tm6J5iI.jpg

I'm not sure if it's just image compression artefacts or that's what the camera is actually seeing before it's processed and sent to users.
To be honest, the repo maintainers.

Unless someone is doxxing, I see no reason for gh to step in.
I think there are a lot of nuance to this statement. After a few years on the start up scene, I believe that if you are using a "duck" typed language your core concepts should be tested without exception (for example rails and django models). The farther you get away from these core concepts, the less your tests need to be there and the more likely that code is to change.

In addition, if you are truly in the earliest stages of your startup (pre-revenue/traction) the tests are not needed -- but you have to be _very_ aware that you are making a tradeoff for sheer velocity and you will have to pay the price later on. I've seen too many startups fail to pay the price and it comes back to haunt them and reduces their overall velocity.
This is incredibly gracious of Lessig, to defend someone who treated him poorly.

I donated to both his ill-fated Mayday PAC and his ill-fated presidential campaign last year. He is a selfless guy who is trying to address the root cause of US political dysfunction.

I wish him the best of luck in his future projects.
Yay, someone actually follows that issue.

If you have the time, you should really consider helping to improve the Rust experience on Windows. There's a huge shortage of Windows developers in the Rust community.
tests can do alot of things, I wish there'd be a more functional name for them, ie. regression stoppers.
I don't know how much stock I'd put in that statement. If management wants to do it, they're gonna do it, despite what the employees say.
I agree that is where the long term focus ought to be.

Do you know if artificial gravity, nutrition and shielding will solve most of the problems?
Capturing Intent – Making sense of code
DeNA ends western development with closure of San Francisco studio
Actually, the PDB debug info has variable and type information and a lot of it actually works. There's just a few minor issues here and there with stuff like fat pointers.
Err, my apologies if that came across as a slight, I literally meant you and a lot of other folks made the exact same mistake. No judgement intended, it's clearly a common misapprehension.

My guess is that a lot of folks got introduced to unit testing through test-driven development and, as a result, conflate the two, assuming the former necessarily implies the latter.

Speaking for myself, I was writing UTs long before the TDD fad landed and so I never picked up the habit. It's just not the way my developer mind works, and I've not found it compelling enough to try and re-train myself.

That said, not believing in the value of automated regression test (of which UTs are the lowest hanging fruit) is utter madness...
It's great such studies exist, but there might be many reasons why they are incorrect (they are testing on students, probably the students don't understand how to apply TDD, or other way around, they are so good that their coding approach provides all the benefits without TDD; the numeric metrics used in study might not adequately reflect the interesting characteristics of the code base, the payback of TDD might show up in later stages of the product life when we refactor or extend it, etc).

Probably TDD can speedup people who otherwise aren't used to iterative bottom-up approach - TDD will encourage short cycle of "change - run and see how it works" loop. Especially in non-interactive languages like C or Java.

Also, if we write tests after functionality is implemented, how do we know why our test passes: is it because the functionality is correctly implemented or it's because the test doesn't catch errors? To ensure test catches errors we need to run it on a buggy version of code. Implement functionality, write test, introduce errors in functionality to ensure the test catches them - that's 3 steps. Run test in the absence of correct code and then implement the code - 2 steps. That's where "test first" might be efficient.

But often that might be achieved other way. Suppose I'm writing a function to merge two lists. I will just do in REPL (merge '(a b c) '(1 2 3)) and see by eyes that it returns (a 1 b 2 c 3). I will then just wrap it into assert: (assert (equal `(a 1 b 2 c 3) (merge '(a b c) '(1 2 3))). Run this and see it's passes - that all, I'm sure it's an OK test.

In short, I think there is a certain truth in TDD, but it shouldn't be taken with fanaticism. And it can even be applied with negative effect (as any idea).

Suppose I want to develop a class (defclass user () (name password)).

I personally will never write tests for make-instance, (slot-value ... 'name), (slot-value ... 'password) before creating the class, the see how tests fail, then creating the class and see how tests pass.

Tests take time and efforts for writing them, and then for maintenance and rewriting when you refactor code. If a test captures an error then the test provides some "return of investments". Otherwise writing this test was a waste.

The tests in the above example will never capture anything.

I tend to create automated tests for fragile logic which is relatively easy to test, so that the efforts spend are justified by the expected payback.

But all my code is verified. Write several lines, run and see what doesn't work, fix that.
He's dumped tons of it at once, on multiple occasions
Keep in mind though, that the study shows that it's no better than testing after iterative development. Testing is still required, and I'd wager that the study participants following the ITL process didn't have external business pressure to skip the "test-later" bit...
Strange that anyone would downvote this. More info on Madoff's employees:

http://www.cbsnews.com/news/madoffs-other-victims-his-former...

Clearly not everyone was in on the "scam" in this instance. I'm not sure why people seem to think that this Indian scam was any different. It doesn't really seem to be giving the employees the benefit of the doubt.

They're told to call a person and say that this person has money owing. They're told that the IRS is their employer. There's no reason to automatically assume that all the call-centre staff are in on the scam.
It's possible. But if you need big space, you're better off in the burbs. Also, lots of your workforce in SV live in the burbs, close to a million along Hwy 101 from Daily City to Santa Clara. And you have another good amount from Milpitas up to San Leandro along I880. So, it's not like people are slogging from SF or SJ to far-out suburbs.
But what would the opportunity costs of that be? Their core competencies are not in "innovating the workspace". There's a chance they could come up with something cool, but an equal chance they'd come up with something bad. For the most part, it seems like doing this is not hurting recruitment.
If anyone else is planning to leave, consider doing this:

git remote set-url --add --push origin https://gitlab.com/name/repo.git
git remote set-url --add --push origin https://github.com/name/repo.git
git remote set-url --add --push origin https://bitbucket.com/name/repo.git

This way when you git push, it pushes simultaneously to all 3.
My claim is a bit of a stretch, 37% may be attributable. Mechanistic cause is still a bit shaky.

G C Buehring, H M Shen, H M Jensen, D L Jin, M Hudes, G Block. Exposure to Bovine Leukemia Virus Is Associated with Breast Cancer: A Case-Control Study. PLoS One. 2015 Sep 2;10(9):e0134304.

G C Buehring, H M Shen, H M Jensen, K Y Choi, D Sun, G Nuovo. Bovine leukemia virus DNA in human breast tissue. Emerg Infect Dis. 2014 May;20(5):772-82.

K Alibek, A Kakpenova, A Mussabekova, M Sypabekova, N Karatayeva. Role of viruses in the development of breast cancer. Infect Agent Cancer. 2013 Sep 2;8:32.

J Akhter, M A Ali Aziz, A Al Ajlan, A Tulbah, M Akhtar. Breast cancer: is there a viral connection? Adv Anat Pathol. 2014 Sep;21(5):373-81.

G C Buehring, S M Philpott, K Y Choi. Humans have antibodies reactive with Bovine leukemia virus. AIDS Res Hum Retroviruses. 2003 Dec;19(12):1105-13.

J S Lawson, B Heng. Viruses and breast cancer. Cancers (Basel). 2010 Apr 30;2(2):752-72.

(Author unknown) Bovine Leukosis Virus (BLV) on U.S. Dairy Operations, 2007.Veterinary ServicesCenters for Epidemiology and Animal Health. APHIS Info Sheet.

J F Ferrer, S J Kenyon, P Gupta. Milk of dairy cows frequently contains a leukemogenic virus. Science. 1981 Aug 28;213(4511):1014-6.

G C Buehring, P M Kramme, R D Schultz. Evidence for bovine leukemia virus in mammary epithelial cells of infected cows. Lab Invest. 1994 Sep;71(3):359-65.
TDD vs. test-after-code is a small distinction.

80% of software development is designing correct abstractions/interfaces/APIs. If you have the correct abstractions, everything else is easy by comparison. And both tests and code are fundamentally founded on these early design decisions.

So whether I do TDD or tests-after-code, I'm confronted with the 80% first: designing the interfaces (either in writing or mentally).

Naturally, I never get this part right at first, and so I wind up refactoring a lot as I go along. ("Build one to throw away", I believe this has been called.)

Now in my experience, TDD requires me to refactor more during this process than tests-after-code. But suit yourself. Changing the order within the last 20% won't be earth-shattering one way or the other.
Similarly -- any thoughts about off-by-one?
> But don't force it down my throat or act like it's the One True Path to clean code.

When I was a programming beginner and started learning about TDD, I was always thinking how soon to start using it because everyone says it's such a good idea. If you would search anything about it, you'd rarely find a resource not marvelling at its surprising benefits (at least, that is how it was few years back). Granted, it may have its merits but is it really a good idea for everything? No way!

One of the anti-patterns I have seen in programming world is how everyone jumps on adopting / advocating a 'good' practice without understanding how it fits the project. I wrote about this a while back[1]. Cue in — git flow, TDD, not using goto, DOM Parser instead of RegEx.

[1]: https://shubhamjain.co/2015/10/26/imperfect-best-practices/
Perhaps it depends on how you implement each. If your idea of test last is writing a full large module and then trying to test that all at once, you might wind up with a different result than if you wrote an individual function or two and tried to test only those at once.

Getting the testing as close in time to the implementation as possible probably makes a bigger difference than first vs last.
I am not sure how you arrived at your conclusion that he is "trying to get Donald-lets-silence-my-critics-Trump into office. What you describe is what MSM is doing for Hillary. Perhaps you are a Hillary Troll. Maybe you are not. Based on this comment alone, I will make an assumption that you are in fact a troll and thus, should be discredited and removed from HN.

Also, you changed your opinion because why exactly? Let's not forget...he is still fighting allegations that would result in his extradition to the U.S. Perhaps he is releasing the docs as is because it provides leverage or at least a faint possibility that the charges could be dropped? Until you are in his situation, you cannot possible attempt to understand his state of mind.
This is not about "city = good, suburbs = bad". It is about "walled garden = bad".

The point of the article is that all those campuses are isolated from the local community, and it is not good because it does not help to develop better infrastructure and it isolates people.

At the end of the article the author mentions 2 SV projects which actually do things differently: Box HQ and Facebook HQ. In SV. Not in SF.

To give you a personal example, what surprised me moving from Europe to SV is the bus service: public bus service is terrible in SV, and what is the answer from big corp to help their employees to commute? Having their own shuttles service... What usually happens in Europe is that the people, the corp, the city, the county etc. interact to build a public bus system. It then allows sharing between companies and benefits everyone. But in the case of those gated communities they do not do that.
In what way is pointing out that Assad has behaved as an enemy to the United States would or that Syria is on the state sponsors of terrorism list (compiled by people with more knowledge than either of us) creating a war hysteria narrative? Are you claiming that Syria is not in the midst of a war claiming the countless lives? Are you claiming that Assad is not an aggressor? If you object to everything as unproven based on the fact that you found a website saying it's unproven, is it even possible to find a "proven" event?
> Wildly new, terse, and clear syntax

Kotlin

> great library of built-in tools that are briefly and intuitively named.

I dunno, guess this depends on what you need. The Java class library has so much in it, but I guess it's not overly intuitive due to the age of a lot of the packages. Personally, I don't think I'd have a hard time getting my .Net-loving colleagues accustomed to everything as is.

Java EE is another matter entirely, I gave up on it after the Java EE 8 clusterfuck that's going on and have just decided to use Spring for everything.

> Easily write and design interfaces that generate both/either back-end or matching integrated front-end code which is off in its own directory and can easily be used by existing JavaScript and HTML.

What are you looking for here? Automagic API's? spring-data-rest says hello. I still find it's better to write my own, but if you need something for a quick prototype there you go.

> Easily scalable.

How are you wanting to scale? Where is your bottleneck? This isn't on the language to solve, it's how you design your application. I can throw up 2,000 instances of an application, but whether the database behind it can handle 100K/tx/sec is another story entirely.

> Relational, noSQL, versioning DB (noms) support.

We've had JDBC, JPA, jOOQ, QueryDSL, etc, forever for the relational story. There's plenty of support out there for various NoSQL databases (Spring even has spring-data-cassandra which I am looking at using right now for an ES/CQRS design).

> Make it integrate with every browser, even some older versions, operating systems.

Why? Java in the browser is dead. If you want to write client-side stuff just use JavaFX and package using WebStart or an installer that bundles your JRE and dependencies.

> Make it compile low-level vs. byte code so it's fast as shit.

Java is already "fast as shit". The warmup time for HotSpot and initializing the JVM is probably the big complaint everyone has, but unless you are writing small command line tools it is a complete non-issue.

With that said, Java 9 will support limited AOT compilation of modules to reduce the time to get basic compiled versions of your classes - HotSpot will still profile the compiled modules, and if finds it is required it will deoptimize, re-profile through bytecode interpretation and reoptimize - just like it does with normal .class files (which are still required to run).
Donald Knuth used an Erlang-like notation
And yet, the end of slavery and enactment of women's suffrage were both strengthened by amendments, rather than supreme court decisions (which is why I included those in my list). So I think that my question still stands. Why would an amendment be necessary to force a right that should've been held by the people already in one case, but not another?
There are 3 countries on the US list of state sponsors of terrorism. It's not an overly inclusive list.
It's been covered to an extreme extent. If Assange isn't a Russian puppet, he's, at minimum, in direct contact with the Kremlin.
Seconded, and you have done so much work on this front. It'd be wonderful if we had more people to advocate for and help do this work.
Also with identical approach there is http://www.actordb.com
Can u show stats of bedrock use in expensify?
How many users?
How many nodes?
How many transactions per second?
queries per second?
DB size?
largest table rowcount?
node failures per month?
how many times have u had a master failure?
network partition incidents?
This is why designing the interface in a language with a powerful type system provides the same quoted benefit of TDD. It helps you think about the interface before you move to implementation.

In my experience, using a type system to do this requires much less effort and refactoring.
Good thing Kotlin already supports reified generics (with the current caveat that they must be used in inline functions), Java the language is less important these days than the JVM having support for the feature.
Are people interested in this kind of content? I'd be open to doing some for fun if there was enough interest.
Just lowered the price to $29 USD.
6'5" @ 230 EconomyPlus on an ERJ gets you access to the bulkhead rows. Just wrapped 40 weeks of IAH-DSM on ancient ERJ's still sporting Continental cabin parts.
RISC-V and the History of POWER
I like Workflowy but wish they would have support to insert images.
And if you look at productivity USA is not beaten by European countries that work less
>Also consider: how many truly innovative companies were ever created in the city and grew to be quite large?

Amazon is one example.
My first pass at this would be to put something like Charles between the wifi AP and the internet and taken a look at what was going on. After understanding the protocol, then would it be a lot easier to look for an OTA FW exploit or mitm attacks around the string manipulation functions used to communicate to the outside.
That's the one that seems to be using illegal GCHQ wiretaps ... see the (Dutch) article below about an Appen translator getting a private voicemail of her ex to translate.

http://www.volkskrant.nl/tech/privegesprekken-van-duizenden-...
How long do you think it is until captioning companies / TRSs such as Captel downsize significantly because of tech like this?
You can't just blame the attacker, it's poor information security practice which enabled the leaks.
Reified generics for reference types is a really, really bad idea. It solves a minor, itsy-bitsy-tiny problem, but pretty much ruins sharing of data structure among languages, because it bakes a specific variance model into the classes. For value types that's not a problem because they don't support subclassing anyway.
It's tedious and repetitive even when the benefit is obvious and substantial, unfortunately.
I'm not commenting on the TDD studies in terms of its effectiveness but I do know that a project that takes longer brings more programming hours which results in larger budgets. If you were a company selling your services, you would be a bit more motivated to include things that take longer especially if this tugged at the emotional sense of assurance in your clients. You would also preach it to your programmers as a core practice and they would happily be converts. This goes for all the structure surrounding your project as well. I tend to see more structure in outsourcers these days and a smugness along with it. I wonder how much of it is bloatware though.
>Make it compile low-level vs. byte code so it's fast as shit.

AOT compilation is not automatically faster than JIT compilation. Java already is fast as shit. If you're worried about that first 100 milliseconds, works is being done on AOT compilation.
I wonder what kind of threats the Obama administration made to Ecuador? Not that I disagree with using pressure to stop someone from interfering in the election process.
I find zero explanation of how to solve performance with a relational model.

As I understand the article, it seems to say...just because all the existing databases you have seen suck at performance when normalized doesn't mean normalization can't be fast.
I'd suggest doing some research if you're curious.

There's plenty of historical material about IBM out there. GE is another great example who even built housing for the management at remote plant and as they moved across the country, military style.