skysight-inc/HackerNews huggingface dataset:
Thanks for the response, and I'm glad that it is better than it used to be.

In GitLab people can have a project without a repository, for example with just a wiki or an issue tracker. For that reason we use different words for it.

Single people also use GitLab as a single tenant we prefer to use the word group over organization. That will also fit better when we introduce nested groups in GitLab 9.0 https://gitlab.com/gitlab-org/gitlab-ce/issues/2772

Good point about showing files by default, we're discussing that in https://gitlab.com/gitlab-org/gitlab-ce/issues/26834

Thanks for using GitLab!
There actually is a problem: There’s countries where "public domain" is not a thing, so the WTFPL becomes legally the same as "all rights reserved".

Which is a problem.
I read a study about Houston recently that actually had another perspective on that. There's not "zoning" laws per se - you can build whatever you want - but there are minimum lot sizes and parking requirements that effectively limit the density of the city to the point where cost effective public transit is impossible. It's not really all that free. I think this was it. [ http://austinzoning.typepad.com/austincontrarian/files/ssrni... ]
Great points. I think it was Mobutu who used to tell Western governments who threatened him: 'Apre moi, la deluge' (pardon my French).

> IT's a tight rope to walk, but there's a system to the madness in regards to presidents: if you punish them to the degree that (parts of) the public demand, you'll almost certainly make it a losing proposition for any of them to ever resign.

I'm not sure that applies in the U.S. 1) We're talking about prosecution under the law, not by popular demand, and 2) being in office doesn't protect them from (most) prosecution, and they can be impeached.
>which they were doing by hand every month

I would assume they just installed python on whatever machine they were originally using to hand-generate reports and the job of that person now is to just run the python script and wait for it to finish.
Looks quite written to me...I just read it.
Yes, it's a good thing. The Swiss are among the wealthiest people in the world because of their high productivity. But "robots take our jobs" makes for a nice headline.
> Portugal is almost a failed state

???

Portugal might be struggling economically (as most of Southern Europe is), but it is by no stretch of the imagination a failed state:

https://en.wikipedia.org/wiki/List_of_countries_by_Fragile_S...
They also for a long time produced the most hard core mercenarys
wrt SVNHub, well, probably you're right. But on the technical level any <insert your DVCS>Hub would be at least nearly as good as GitHub. And git didn't invent DVCS.
I know I've spent hours trying to get Ruby setup and figuring our why bundler install failed, so disagree with your "fifteen minutes" comment. Maybe in the best case scenario.
That may be technically true but in practice and rhetoric "unsafe" is often used in contexts with much broader, implicit connotations. For example, putting Rust-compiler-proven-safety as the top, first, or best feature to consider. In that context, saying "C++ isn't Rust-safe" is essentially defining Rust to be "better", not advancing a coherent argument that it is in fact better.
I bought mine for 2000 PLN, in cash. I had only wanted to buy one for the novelty value, but when my friends asked the seller if he'll miss his Maluch, he said “well, I'm 86 now, and I can't drive anymore.”

I was heartbroken, so I just gave him the money and took it off his hands. Here's my little baby: https://www.instagram.com/p/BHKiB4Qg3pi/
14 years ago I told my teacher at a very respected uni that real-time facial recognition would surely be used by gov for security.

He said I was insane and that this would be extremely hard to implement and it was very improbable that it would ever happen. He basically demoralized me in front of my colleagues.

Needless to say he failed to convince otherwise and I lost all respect for him.
That's not true at all.

I suspect that, unlike my own country, they enforce and respect the immigration laws on the books - truly a shock.

However, even outside city centers you run into people of all types. On my last trip I found myself in Gruyere and there were muslim families and east asians touring at the rest stop.

Inside Zurich there's a roughly Minneapolis-level background of racial diversity.
Google lancia un nuovo servizio di database distribuiti in cloud
> more cash is spent in social services paid by fuel taxes

That might be the case in Europe, but it's not true of the US. Here fuel taxes only cover about 50% of the cost of roads with the rest coming from the general fund.
> Everyone wants to use the fanciest data structures when most of the times arrays will be faster and simpler to use.

I'm not sure I comprehend this, since I don't often encounter code where people use advanced data structures to do simple things. For most collections, you're typically talking about an array of some kind, since you just want to iterate through many objects doing the same thing. However, there is a reason for more complex data structures to exist. KDTrees, for example, are great for performing nearest-neighbour search, and I can't see any situation where I'd want to use a straight array if I knew I was doing nearest-neighbour searches.

In the most broad, general case I agree: array-of-struct or struct-of-arrays is probably the way to go. You can even see this in the data science world where data frames (effectively struct-of-arrays) are the tool of the trade. However, there are algorithms where if you want an advanced data structure, you really want it (e.g. KDTree). Is it really so common in systems programming to see people trying to incorporate all sorts of magic from The Art of Computer Programming into their programs? I can't say I've ever seen it myself (obvious disclaimer that while I'm a programmer by trade I don't read too many large Rust / C++ projects).
Glad to hear you're considering using GitLab. We have an importer for Gitea but not for Gogs https://docs.gitlab.com/ee/workflow/importing/README.html so I think you might consider a batch import https://docs.gitlab.com/ce/raketasks/import.html
Indirectly. We have a URL that shows comments by a given user that we've replied to.

I've been meaning to generalize this and make it available to everyone, so you could look up "replies to John by Mary".
Another cool example: solving differential equations with opamps

https://www.youtube.com/watch?v=DBteowmSN8g
"that's very easy for me to either quickly draw on paper or imagine it in my head"

Good point, but it's only easy to draw or imagine if you already know everything involved. In my opinion software visualization should not just be about visualizing what you already know but instead about providing information that you don't know. So you don't need to go through all of your code files in order to draw that inheritance diagram.

"number of users are not visual"

I think I don't know any programmer who hasn't already scribbled some kind of diagram on a piece of paper ;)
There will always be 1-2 queries that can be proven to work better in an alternative query language, other than SQL. For instance, I can surely find a couple of awesome graph queries in the Cypher query language (Neo4j). Or some JSON queries in N1QL (CouchBase). Back in the days, they tried to advocate that QUEL was a BetterThing™. Where's QUEL now?

Same will be said of LINQ in a decade. Whereas SQL will still be there.
I once referred to Czech Republic as part of Eastern Europe to a Czech and was swiftly corrected. He felt it was Central Europe. I was grouping it as 'formerly Communist', but I'm sure Kafka would find more in common with Germany than Serbia. These definitions shed little light. Reading Hasek, even concepts like Austria-Hungary are nearly useless beyond knowing where the taxes go.
That's a different question and I think the answer to that is obviously complex, but a lot of it is luck. If the Dutch and Portugese had shown up in the Indian ocean while Ming were still engaged, they would have had a rude shock. Otherwise, historians have looked at factors like the location of iron in China (further from population centers) and timing of major epidemics. One really interesting book is

https://global.oup.com/academic/product/before-european-hege...
CIG switched to Amazon's Lumberyard fork of CryEngine, which I suspect will become the canonical upstream, provided Amazon keeps up it's support and doesn't alienate people with crazy Amazon service tie-ins. My (not very in-depth or researched) impression is that the original team at CryTek suffered a brain drain long before this latest round of financial difficulties (e.g. lead engineer Tiago Sousa moving to id Software to succeed John Carmack as lead renderer guy), so I suspect they don't have a huge the "real change is happening in this branch" advantage over Lumberyard anymore, and Amazon is surely more stable than CryTek is.

Note I'm not working inside this industry, this is just pieced together from news observation.
I'll let you know. There's a newsletter for major updates, or you can ping me via email (in profile).
> All in all, it remains true that Rust doesn't really provide any safety above C++ in regard to writing these kinds of node-based data structures

Debatable. It certainly does for the consumers of these structures, and data structures are consumed a lot more often than they are rewritten.

> Yes, Rust has some downsides and tradeoffs. Is it so bad to just say that out loud?

Of course not. But that doesn't mean you shouldn't expect some pushback if you're incorrectly describing those tradeoffs.

Is it really so bad to say "at the end of the day, the difficulty of complex graphs in safe Rust is symptomatic not of a flaw in Rust but of how hard it is to build these things without memory errors even in C or C++" out loud?
I'm exactly the same way, and as you say, I don't expect that my antics would give a state actor even a momentary pause. I'm more concerned about doxxing, or other low-level junk than jackboots kicking down my door. It is a little inconvenient, but it's worth it.
He said just the CUD part (Create Update Delete). The assumption is that your data can be entered manually through the Sheets UI and your code only needs to do the Read part.
Some notable organizations are planning not to move and more or less forking: https://opensource.googleblog.com/2017/01/grumpy-go-running-...

Python 2 will be with us for a long long time.
The problem with naked short selling is the ability for rampant, cheap, and extremely profitable manipulation to cause "artificial" price-drops. There is basically no penalty for failure-to-delivers and companies share price can be gutted while no real shares have been traded.
Great stuff. The lack of surface and volume plotting was one of my perpetual gripes with matplotlib.
How is 'reasonable' different from 'rational'? And don't both these terms beg the question of ultimate ends and/or values?
I literally cannot imagine paying $500 a month for a car payment

Why not? Consider: I got a Subaru Forester with $0 down and 0% interest which I pay off over 4 years. With options, it's $650 monthly. Again, no upfront costs.
If the management (or other owners if it's a condominium entity) finds this problematic, they could always institute a rule prohibiting short-term rentals.

Otherwise AirBnB usually drives up prices in highly desirable locations, and for someone renting on the cheap it's a canary in the coal mine - the rental rates in highly desirable locations will go up anyways.
>Old jobs are always replaced by new (and usually better ones).

No, that's just what happened a few times in the past. Not some natural law. The previous times farming jobs got replaced by factory jobs (which were enough because of a huge increase in the manufactoring sector) and when those dwindled by robots and more efficient factories, they got replaced by the services industry. This time automation and software/AI depletes factory and service jobs, and we don't have much room for any other kind of jobs.

Any job we'll come up with will either be able to be done by robots, or be replaced by advanced AI. The exceptions where human touch will be still (always?) needed (artistic work, prostitution, etc) are not enough to make a living even today, much less in an oversaturated future market.
> Nixon was already shamed

Lots of criminals are shamed; that never relieves them from trial and punishment.

> it would have served the country no good

I disagree. It sets a precedent that the powerful are above punishment and reduces deterrence. Now Presidents know that they can do almost anything and not be tried for it.
I agree with you on all sentences but one.

> Also, War has undeniably driven technological advances throughout history.

The opportunity cost of a war is huge. It can easily be argued that it is larger than the perceived gain of a war. Objectively measuring those two costs is another matter, but there is nothing undeniable about it.

Let's pick WWII as an example. Rockets came out of it and put people on the moon. What if we had peace instead what would those rocket scientist have done instead? Likely they still would rockets and other vehicles, but their would have been input from more scientists and it would have taken a few extra years while those scientists made other things. The moon would have happened anyway, but probably in a more sustainable way than a postwar "space race". What about Nuclear power? Maybe delaying that a few years might equal the economic output of the two cities it obliterated. Another view, without the specter of nuclear war we could have built more of the cleanest and safest power source we ever devised and redirected all the labor on coal and oil to other areas that nearly limitless energy might provide.
I think this misses the problem.
Should you write your own data-structures?
Not unless absolutely necessary.
But mostly everyone knows that.

So why are people complaining about data-structures?

For me, writing the data-structures is the canary in the mine.
It's the next step from hello world when trying to pick up a new language.
Most importantly, trying to write a few simple data-structures hints at the difficulty that will be encountered writing a 'real' program.

For people like me, if writing trivial data-structures in Rust is a great challenge, it shows that writing other, less trivial things in Rust will be much more challenging than might be preferred.

Hand waving the comment "writing data-structures in Rust is hard" with "well you shouldn't be doing that anyway" misses, I think, the point that Rust (while very neat) is generally a difficult language to pick-up.

[Edit]

Again, the issue isn't data-structures or about them.

The issue is: Can I write something in scratch in this language 1) at all and 2) with some amount of daily progress.

Writing data-structures is a test case of my ability to thing and program in the context of Rust. It serves to answer the question: Can I write a program that implements a well defined, well understood construct so that I may learn the building blocks of rust?

This leads up to an application, the behavior and design of which may not be extremely well defined in the context of Rust and requires more thinking when working out the data-structure in rust.

If the answer to "can I write a data-structure in Rust" is "Ya totally got this makes sense" then writing an application will be relatively easy.

However if the answer is "Wow I did it but there were a lot of pain points and I still have no idea if I've done it in the right or canonical way" then writing an application is going to be very difficult.
It's fascinating that the financial system has evolved this kind of layered abstraction (humans owning stocks is a fiction maintained by brokers owning stocks, which is a fiction maintained by DTC owning stocks, which is a fiction maintained...) reminiscent of hallowed engineering kludges like TCP/IP. Its especially interesting since, unlike data packets, stocks are purely an abstraction to begin with, but the systems around them have become sufficiently complicated that it can't function without this kind of structure.

A blockchain likely wouldn't help this issue either- high-speed traders would inevitably be dissatisfied with blockchain latencies and re-invent brokers that abstracted over blockchain transactions at a faster pace. These brokers would wind up causing bureaucratic meltdowns and become managed by some overarching structure similar to the DTC. Etc. If anything, a blockchain-based system would become more complicated, because it reduces the task of adding another financial sub-mechanism to an engineering problem.

Something about large distributed systems of non- or imperfectly-cooperative agents breed complexity. (There's probably already formalized versions of that principle, but none are presently coming to mind.)
One explanation is the book "Triumph of the West" by Roberts. He makes the case for it being the culture.
Ask HN: Is there any proven model that eliminates corruption?
You hear about more and more corruption from people who don't lack anything. Seems that entire systems are corrupted.
Do you know what we call an area of land with lots of metal? A mine.
If they want to grow beyond "just a team chat app" that takes a lot of engineering talent to do it quickly enough to compete with MS, Google, FB, etc. who are all moving into this space full force.

Additionally, to sell into the enterprise you need a sales team, so a lot of those are probably sales people on commission.
> All in all, it remains true that Rust doesn't really provide any safety above C++ in regard to writing these kinds of node-based data structures,

Yup! Rust does not fix all your problems, sadly. Maybe some of them. :-)

If you're working with graph-like structures in Rust, then you have two choices:

1. You can work with pointers using 'unsafe' blocks, and then wrap everything inside a nice, safe API. This is a good tradeoff if your data structure is only a tiny portion of your code, or if it's reusable. (Most of the data structures in Rust's 'std' crate are written like this.)

2. You can work with indices instead of pointers. This is the approach taken by petgraph (https://docs.rs/petgraph/0.4.3/petgraph/), which is currently one of the best graph libraries for Rust.

Not all Rust code needs to be safe. It's OK to write "unsafe" code and put it behind a "safe" API. If I can eliminate 98% of the opportunities for pointer bugs, I'm happy to eyeball the remaining 2% manually.
How often do you really need those interesting structures(and the memory fragmentation that comes with them)? I've seen countless times where a developer reached for std::hash_map/linked_list when there will never be more than 10 values in their dataset. In that case an array would be at least as fast and much easier on your data layout.

Also if you're trying to implement lockfree data structures then safe/unsafe pointer access are going to be the least of your worries :).
So this was one of my last year's goal. Here is how I achieved that $XXX/week extra in saving.

1. Switch to debit card and pre-assign how much you want to spend/month: A translation I made on Credit card was paid automatically in full by the end of the next month (due date), that made me not think about what I am spending on at all. Using debit card (simple.com) made me think after every transaction.

2. Set goals if you want to buy something non essential: I use simple.com for this. If I wanted to buy something, I would first set a goal that I want to save up $300 in N days. This reduced by impulsive buying habit. I still buy few books randomly but you can cheat at times (try BookBub.com, really saves money on ebooks).

3. Map out your cashflow: Just create a note of your incoming cash (after tax). Now send x% of high yield saving account (I use barclays bank), x% of monthly expenses (rent/mortgage/food etc), keep a little in your checking account. This helps you understand where your money is going. Its ok if you are not able to save much, the key is first tracking it manually (mint.com etc is great but start with a simple note).

4. Invest a part of your cashflow: I am not a huge fan of investing all my savings (after 401k): So I invest about 10% of my cash after tax to an index fund on Vanguard (you can use betterment/wealthfront too).

These 4 things gave a much better overview of my finances and where my money is going. This doesn't mean stop spending less (difference b/w being frugal vs being cheap) but at-least start understanding how to deal with money.

Hope it helps.
>That's great that this is getting upvoted at HN. I started studying software development last November, at the age of 37. A few times, in my own and other people's posts stating that we are learning to code, there was more negativity in the comments than I would expect from HN.

Ignore the naysayers.

I started to teach myself programming around my 35th birthday. About a year and half later, at the age of 36.5 years, I got my first professional programming position. It was nothing sexy. It was doing maintenance programming on LOB applications in a corporate IT shop. But it got my foot in the door. And I kept on teaching myself, absorbing as much I could about every technology I encountered. My career has been on an upward trajectory ever since.
Stock: https://www.google.com/finance?q=clm

http://finance.yahoo.com/news/cornerstone-funds-announce-con...

Supposedly has an 18% yield, which is pretty darn good. What's the catch?
Kind of seems like you're on a hidpi display and the game isn't aware of it. (Or maybe the buffer that mesh is rendering to, but it seems like you've covered that and I don't know Unreal well enough to suggest otherwise.)
Traveling abroad, taking a sabbatical and deciding to go remote
I went pretty far down the path of trying to build applications with Google Spreadsheets and Apps Scripts (we still have some major business processes running on it). It's definitely made me feel the need for something between Spreadsheets and custom development or Salesforce - something like what I imagine MS Access solved in the earlier days.

Here's what it'd need:

- Spreadsheet like UI
- Validations and field data types (major liability of spreadsheets)
- Good forms integration
- Custom code like Apps Script capability
- Something around workflow and business logic

I think Airtable gets pretty close but I haven't been willing to switch cause of some limitations but I do like where they're going. I'm considering pulling the trigger for Salesforce but keep hearing that it's really easy to shoot yourself in the foot.
I'm the author of another React static site generator (https://github.com/gatsbyjs/gatsby).

I totally agree that for many sites, using Phenomic or Gatsby would be overkill.

But for something small, it doesn't really matter what tool you use as long as it's familiar. For small projects, familiarity trumps any other concern.

React came out of Facebook that needed a frontend technology that could scale to 1000s of developers.

Gatsby and Phenomic are both an attempt to port the best of the React ecosystem to the world of building web sites. They're designed so that as your website gets larger and you add more people, the code still feels simple and it's still easy to make changes and add new features.

So yes there's a learning curve and some overhead but it really pays off for larger projects.

And the nice thing is that once you understand them, they're now familiar so just as easy to use on small projects as any other solution.
And even the cuckoo clock is from the Black Forrest, Germany, rather than Switzerland.

But seriously, the Swiss have lots to be proud of.
lld is the LLVM linker. More details here:

https://lld.llvm.org/