skysight-inc/HackerNews huggingface dataset:
I've done space projects with US companies and so am fully marinated in ITAR processes. In answer to your question: No, you can get around ITAR by just being careful about what information is imported and exported to and from the US. If there was a US engineering office and an NZ engineering office and all the engineering effort was evenly distributed among the two, it would be a nightmare as you'd be 'exporting US technology' constantly, but if all the important stuff is being done in NZ and very little know-how has to go back-and forth across the virtual border with the US then it's more manageable (still involves lawyers and experts though). It doesn't matter than the US owns it financially, it's the transfer of knowledge and stuff across the border (virtual and real) that is the hard bit. As this is basically a NZ company which had to do a paperwork fudge in order to accept US investment, ITAR is not such a problem.
Thanks for this - I'll try it out, I hadn't realised you could have one app on multiple virtual desktops!
> I didn't put it higher on my priority list because to me it looks like it focus too much on being a "community-driven website" instead of providing a solid service as a media-hosting/publishing/catalog system. To me it looks like they are shooting for the wrong level of "decentralization granularity". Each instance of these services are aiming for a "community", and think that the people use the mainstream tools because they don't want to/won't manage the server. The point they seem to miss is that this only creates another type of top-down organization. It would be MUCH easier for them to focus on a "single-user" system, and start from the point that the communication will work when the applications talk with each other.

This 1000 times. It just kills me to think about how much potential progress has been lost to these major projects spending so much time and energy on social federation protocols instead of working on the actual primary function of the software.

Mediagoblin could have already been THE software go-to for personal media organizing and display, but it seems to be getting stuck like every other potentially great project that runs out of steam when the main developers lose their focus. And now Yahoo has sold assets to Verizon, and millions of Flickr users are wondering what will happen next.
>Most importantly, the saga of Dash being banned from the App Store, and the author's blatant attempt to use the community as his private army in an attempt to blackmail Apple, have completely ruined his reputation and any goodwill he may have had at some point

Why would that "ruin his reputation"? Seems like a very OK and logical act: get your users to add their voice against the mistreatment of their app by some store's policies.

ADDENDUM: Hmm, reading into the story, the actual issue is false promoting his apps with fake reviews, not that he tried to use the community to help his case with Apple. The problem is that his case was problematic in itself.

[EDIT: not related to Karelia software -- mixed-up Kapeli and Karelia]
Yeti is here to enlighten your Smart Home
I don't think KDiff 3 looks native anywhere, and I don't think it's because of Qt.
It uses weird fonts and icons, and for some reason their toolbar buttons just look wrong.

Still an extremely useful program.
Naive question: is something like AlphaGo also better at chess compared to previous approaches to chess? Can someone elaborate?
The novelty of "building spaceships" rubs off very fast.
I don't get this logic that much.

Your neighbor left their door unlocked. You have their phone number. You can call them to tell them first, and make a funny FB post about the event afterwards. Or you could just post about it on FB.

Not to mention that the users of the software are the ones who suffer the most. Seems pretty ethical to at least try to get the issue fixed.
Microservices are just one option of refactoring that can be considered at later stage of life of the system.

Even big guys who are using microservices started with monolith. Many people can't seem to catch this important detail - they started as monolith that was later refactored/modularised/split/microserviced. It doesn't mean, the moment they did it, that humanity found a better way of writing software called "microservices". It just means that, at that stage of life of the project, it made sense. Starting with monolith is still, in most cases, the best way to write projects, even if later they evolve into microservices.

Starting projects with maximum split into microservices is, in most cases, just a plain, stupid idea.

The most important part when starting project is avoiding friction at all levels - from dev setup, contribution, deployments, database evolution (migrations), interaction between different parts of the system (it's easier to just call a function from a module than to do rpc - which involves implementing rpc on the other side, managing it's deployment, keeping interfaces in sync etc)...

Microservices are for mature services with crystallized interfaces. They emerge naturally and the split is obvious at later stage - this information is not available at the beginning.
Zomato: Security Update – What really happened? And what next?
(btw there's `pdftotext`, which is pretty good in most cases)
> Self (along with Scheme) was supposedly one of the big influences on Brendan Eich when he was creating JavaScript.

That's really doubtful. Self's delegation-based inheritance was expedient for quickly implementing an object model instead of having to build a class system, the influence never seems to have gone any deeper.

The one big influence on Javascript was Scheme, that was the original idea, when Netscape's execs asked for a more java-style language for marketing reasons, special-casing a single parent slot was an easy way to bolt an object system into the thing.

From what little I looked at it, delegation (through parent slots) is everywhere in Self, it's used for inheritance but also for mixins and scopes chaining and… It's not just an object model, it's a core semantic principle and tool.
Ah, kool. I first need to finish this up to a stable state though. Right now it just barely passes the benchmarks test.
>while all the engineering, design, manufacture, operations, etc. are in NZ

I'm not sure how Rocket Lab splits design/manufacturing but they just moved into an pretty sizable facility in Hungtington Beach, CA a few months ago and I know for a fact that they have engineers and technicians on staff there.

In any case it's great to see them progressing.
Sounds like they spend a lot of money on questionable "marketing". Also, one never knows where the true profits are recorded in the days of ubiquitous tax avoidance.
Are all the engineers Non American citizens then? Wouldn't trying to hire American citizens also be a nightmare with ITAR?
TDD is informal, I was thinking about something a bit more mathematical. It's hard to reason about spaces with TDD.
Relax already.

We say "prototype" to indicate an important feature of Self which its children (Python, JavaScript, etc.) inherited: Unlike classes, prototypes are open for modification. The precise mechanisms differ between the different languages in Self's family, but they all have that feature in common.

Compare and contrast with other Smalltalk children, like Java or E, where this isn't possible because classes are closed. (E doesn't have classes, but it has a similar property, in that object literal scripts are closed for modification.)
Mankiw is a bit of a right wing nutjob, though orthodox in the Chicago school. I wouldn't recommend his books, despite their prevalence in academia.
But there was no reasoning given as to why he had his account disabled. Facebook is now so ubiquitous that it is in danger of becoming an essential service.
Nice work! I'd be curious to see a comparison w/ RabbitMQ's MQTT extension. By any chance have you done such a comparison? Also I assume the comparisons are done at QOS level 0?
Have you tried SPARK Ada? It was first to be designed to automate proofs of common attributes such as immunity to lots of code injections or crashes that happen in C. They have both automated and interactive proving for other conditions you put in as preconditions, invariants, and postconditions. Need more people building reusable specs and code in such languages. Others from Microsoft are VCC compiler and Dafny language. From CompSci, Frama-C and Jave Modeling Language.
Having worked on over 100 DevOps initiatives, I'm inclined to disagree.

8 years into DevOps, automation, cloud computing etc, it's time to accept that DevOps is a specialism and a function that companies - especially big ones - need to put into place in order to adopt the principles.

See here for further thoughts - https://devops.com/im-happy-devops-engineer-job-title/
Yes, hardly, because there is little chance that Assange is going to confirm this.

We don't even know for sure if he actually knows something or simply pushes for investigation of this murder solely because other leakers are worried that this conspiracy may possibly be real and that the same could happen to them.

Or because his room in the Ecuadorian embassy is too small and he would prefer to live in Moscow with Snowden /s
Turns out I was mistaken. If you look at their careers website (https://rocketlabusa.com/careers/positions/) it seems as though the engines are being designed and/or built in California and the rocket and software is being done in NZ.
I agree. But the flipside is that without patents, no-one would be spending money on drug development, since there would be 100% probability that someone straight-up copies your drug that you spent 5 years and $50 million to develop, and can then sell profitably at a lower price and capture the market.

I think we can all agree that drug patents in particular are a necessary evil. On other patents (in particular software) I'm a lot more skeptical. And that's not to say "Big Pharma" isn't trying to abuse the system to maximise their profits.
When they first announced the design I know a lot of people in the industry were skeptical that it would work at all.
Tetris MicroCard, powered by Arduboy
They contacted Google on August 22nd, 2016 and Google decided to do very little about it. At least we know there is a problem now and we can take mitigation actions.
Online gold jewellery
Maybe it's time to see if we can get vendors to adopt fwupd, or something which can rely on the same dataset, as a standard cross-platform mechanism for updating firmware on devices which can conceivably be supported.
I imagine it would take a considerable burden off of those vendors; marketing it as such has a decent chance of success. Not sure if Richard Hughes (thanks for assembling my ColorHUG by the way, if I go back to work in the next month or two I'll definitely get a ColorHug+, since I'm interested in verifying open source scanner calibration workflows) wants to make a living maintaining a firmware updater, though. It'd probably have to be somebody else.
How Our Startup Nearly Died in the First 6 Months
Is Swordfish the worst hacking movie ever?
> Well, they banned you because they want you to stop posting inappropriate pictures (as defined by their TOS).

No, they banned him because they can do what they damn well please, and their approach to content moderation starts with a hammer and escalates from there. It would've sufficed to delete the offending post and issue a warning, even ban him from the group where he misposted the nude. Completely severing access, for a week, from a primary means of social interaction, is vastly disproportionate - that's something you do because someone has demonstrated a clear pattern of deliberately shitty behavior, not because he got loaded and acted the fool one time.

Considering the extent to which Facebook has inveigled itself into so many people's social lives, and the consequent scope and impact its moderation actions may have, I think it's long past time that some severe regime of external regulation be imposed on the corporation, whether by legislation - although that's a forlorn hope at best in the US, where Congress is largely useless no matter who's in it at any given time - or by shareholder activism, as someone else here suggested. I'm not the man to run that project, but I'd surely buy a few shares to participate in it.

To be clear, I don't want Facebook fixed, because I don't think it can be. I want Facebook gone, engineered out of profitability - and thus out of existence - and replaced with a world in which no new Facebook can arise because everyone can both own her data and identity outright, and participate in what we now call "social networking" without having to make herself beholden to any corporate behemoth at all.

It's possible! There are a lot of smart, capable people working on it, and more join in every day. Eventually, someone's going to hammer that stake into Facebook's heart. Before then, finding a way to enforce nuance upon it is a good place to start. Facebook hurts people every day, and cares not at all that it does so. As we work toward the ultimate goal of killing it, we do well also to reduce its ability to do this sort of harm.
How about prizes as a way of funding R&D? It's a different kind of profit motive, and it doesn't rely on monopolies and rent extraction to make things profitable. Once a drug is developed, it can be reproduced at close to cost.

https://en.wikipedia.org/wiki/Prizes_as_an_alternative_to_pa...
Well, I have one powering my mobile phone radio station.
Not always. A player that thinks he will lose a game that's tied in the last 8-ish moves will have an incentive to create a highly unbalanced game. That way, that player gets a 50% chance of winning.
Im calling the police!
So could we use this mechanism to treat auto-immune disorders, or prevent organ rejection?
More evidence that betting against vaccines is not a good idea...
For me "SOA" doesn't imply "an ESB" in the way you seem to understand the term, and even though I've actually worked with Sonic MQ/ESB which brought the name to the scene, I still don't know what people really mean when speaking about "an ESB".

From a developer perspective, service-oriented just means that you're offering/accessing functionality via a well-defined app-specific network protocol interface with a standard taxonomy/representation of cross-cutting concerns such as auth, transactions/compensations, message synchronicity and QoS semantics (eg. request/response, at-least once delivery etc.), most of which define the shape of your service implementation code fundamentally. For example, if you're operating under the assumption that no distributed transactions are available, you'll have to fold the necessary logic for restarting and state management into your application code.
Vue is more like Angular 1. Not sure about Angular 2 and higher - never used them. So if you are familiar with Angular, you'll get into productive development with Vue much easier than with React.

I think all of these libs and frameworks are trying to solve the same problem. So I wouldn't bother much on trying to understand what is the best one. It's more a matter of preference, project and team requirements.

React has a bigger community and ecosystem, but Vue is getting mature very fast and also has a lot of necessary tools and libs around it.

I really like Vue and use it in my pet projects. It's easier to get started imo and it's self-sufficient. When React is saying that "this is just view library", in reality it is used with a lot of additional libs, which you need to get familiar with. And it makes it harder to learn for me, because there are tons of alternatives among those libs.

I may be biased though because React was the first library I learned and Vue was the next one.
I also noticed that after military service.
In the service, I had two uniforms that were exactly the same that I wore every day. At first I hated the uniform, but after I finished, I realized how convenient it is to not ever have to think about your outfit at all.
I sort of practice this now as well, with a well defined 'base' of jeans and a shirt that doesn't need ironing.
Two approaches used by the previous version of AlphaGo (MCTS and a NN for position evaluation) have been tried in the past in computer chess with relatively poor results, while in the past few years they were already giving good results for Go.

The current version might be using some different techniques that could be more useful, though. They should release some details in the next few weeks.
We seem to be an industry with a severe lack of professionalism.

We fail to manage risk, we neglect security, we rarely know we are regulated and we hold an air of contempt about the idea of being asked to pay for our failings like any other industry (car manufacturer, drugs, etc). It's too hard to make perfect software, but really easy to make everything else?
The list goes on... We have made huge innovations and made real impacts, but we largely aren't doing it safely or respectfully and our attitude to privacy is horrifying.
You might think you are okay, but look around you: look at the security of how you deploy, the missing tests, the broken accessibility, the trove of user data in your company, the code maintainability strategy, the lip service paid to copyright, the sheer number of hacks, etc. There are many who would like things to improve and many who challenge the norm, but that challenge will never be formalised until we lead from professional bodies spearheading how we should do things, rather than corporate bodies and celebrities pushing their agenda.
When the product is really important, we should change how we reward development, because if it's expensive, and we grant a monopoly, then the benefits of the product will be concentrated with the wealthy, rather than the many. And yes, that's not a good thing.

Consider prizes instead of patents: https://en.wikipedia.org/wiki/Prizes_as_an_alternative_to_pa...

We don't need to have a government enforced monopoly to support high prices to fund drug development. There are other ways that don't turn it into an economic ghetto either.
I agree. Microservices enable startups to pivot very easily, or to implement or diverge into new sales channels quicker than with monolithic solutions.

The same applies to larger business. With microservices, ie. large banks can easily offer API services, enabling new revenue streams that were nearly impossible to offer before.

Microservices are an excellent way to deal with future changes. The unknown unknowns like some would put it.
I have in fact tested RabbitMQ but it was not at all impressive. The two fastest brokers I have found are emqtt and Mosquitto, both good at either large or small broadcasts but not both.

Edit: yes they are qos 0 (just like Redis)
It is going to vary quite a bit depending on the entropy of the ASLR implementation. Many have only had 8-12 bits of entropy to start with, and you sometimes don't need the full address. It is also important to note that services that crash typically restart, allowing retries (sometimes as many as you want). In this case, one might imagine trying to attack thousands of people: some of them will randomly work (and a lot of users are going to see VLC crash and will retry playing the file a number of times, increasing your probability).
It is very outdated. https://wiki.mediagoblin.org/EasyDeployment#Sandstorm
So has Mac OS, since 2007 (the implementation wasn't perfect, though, and possibly still isn't perfect)
Go 1.8.3 is released
ECON101 isn't 'mainstream economics'. It's incredibly simplified economics.
why does it say notational-velocity in the URL if OP claims it's inspired by it? Is it used its database for backend?
I mentioned this elsewhere but sandstorm packages are simply not updated at all - https://wiki.mediagoblin.org/EasyDeployment#Sandstorm for example. But this is true for vast majority of the packages.
Just Keep Scrolling: How to Design Lengthy, Lengthy Pages
You can view there being 5 dimensions/concerns with large scaling factors containing issues needing solving to be generally applicable.

1. How to search
2. How to resolve breadth concerns
3. How to resolve depth concerns
4. How to resolve large training requirements
5. How to form and resolve recursive goals

With AlphaGo, it looks like they may have solved 3

1. Search. Monte Carlo will likely be used from here on out. Much more efficient than full brute force search (chess style).
2. Breadth - Policy network. Reduced branching factor from 250 to between 5 and 10.
3. Depth - Value network reduced depth from roughly 75 to < 20

Next they're working on applying reinforcement learning to their two NNs. Ie seeing if they can optimize how well they can do and how quickly they can learn. Maybe there are large gains there.

If so, the final task would be finding a game or situation that required nesting of sub-goals like everyday life does.

They've made some impressive gains.

> In reality, unless you have a really good simulator, deep reinforcement learning is almost never applicable.

I could see Deep Mind applying this to something like catching a ball in the near future. Just to show it's generality. It's not that different of a problem space than learning to play breakout.
Release notes: [0]

Release timeline: [1]

Release milestones: [2]

[0] https://golang.org/doc/devel/release.html#go1.8.minor

[1] https://pocketgophers.com/go-release-timeline/#go1.8.3

[2] https://github.com/golang/go/issues?q=milestone%3AGo1.8.3
I didn't say all people who use it are idiots. But willingly sharing your private data for free while waiving all your rights? If you realise that facebook runs AI on that data and knows much more about you then you could ever imagine, and if you realise they are selling that data to companies you might not like so much, or what else more, that's pretty stupid imao.
I would assume most of their employees in NZ hold NZ citizenship although I'm unsure exactly how NZ handles ITAR.

They have engineers/technicians based in the US as well and I would assume most of those are US Persons (US Citizens or Permanent Residents). In the US you can get ITAR exemptions for non-US Persons but from my understanding it's a more difficult and much more expensive process so it is only done to recruit very high level talent.

I'm at SpaceX, which is a much larger company than Rocket Lab, and I can probably count on two hands the number of non-US Persons working here.

I'm fairly certain that Peter Beck, Rocket Lab's founder and CEO, who is a Kiwi, lives in Socal now.