Fredej

I would love to have a way for my bank to hold my crypto for me, with the same amount of insurances and security audits as they have for other assets.

The "be your own bank" idea which crypto offers was one of the reasons it has taken me a while to get into it. That was something that I really didn't want.

I trust my bank living up to the task of keeping it safe and reimbursing me if they don't. I don't care about the individual coins but I do care about the value they represent and I trust that even if a bank loses a number of coins that it will not affect me. Just like if a bank vault was broken into it would not come out of my account.

Not to mention that most of those have servers in the EU which will not be affected by this. Sure they could raise prices there, but since this would just subsidize US costs a local competitor would have a competitive advantage.

What this non-Net Neutrality does is largely saying "if you want to build an internet-based startup the US may not be the place for you".

I disagree. As a private person I would feel a lot more secure if I could pay someone to safely hold my cryptocurrency for me.

I trust my bank a lot more than I trust myself to keep things safe.

This seems to be a controversial opinion in the crypto-space :)

Just a single outside lawyer we consulted with :) We already had processes in place for dealing with BSD.

The reason for consulting with a lawyer was to ensure that we didn't do anything wrong which would later require us to open up source code that we didn't want to open up.

That's true. Releasing other open source software using GPL software is much simpler. But if it's desirable to deploy closed source software GPL may not be the right choice unless you have time to sit down and consider the legal ramifications. In many cases there may be none if you use it in the right way but it should be and is being considered when companies decide consider whether or not to use open source software.

That part is often significantly simpler with BSD which is why it's significantly easier to just allow BSD and have a case-by-case basis for GPL.

Where do you get the $150,000 figure from?

I would disagree that the situation is the same. The way to remedy the BSD situation is simple attribution. The way to remedy the GPL situation is release of the entire source code.

>> Worse, the source code of all versions from _before_ that checkin automatically become GPL-licensed (because they contain code that, transitively, becomes GPL because it later was linked with GPL-licensed software) >This is simply false.

Is it? If you are forced to release all your source under GPL any new release of that software will contain software released under GPL, even if the GPL specific changes are rolled back.

My interpretation is this: If you have two functions, A() and B() where A() is released under GPL. If you then release software where B() is defined as :

B(): ... A()

You now have a product which is a work derived from GPL code so you must release the source code for B(). Now you release B() under GPL. So you go back to the commit right before including A() and make a new branch with a new commit:

B(): ... C()

BUT! B() is now source code released under GPL so any changes to it must also be released under GPL.

How have I misunderstood?

The process was figuring out that we in no way mix any GPL code with our own code. As long as we don't do that it's fine but we still have to make sure every time we touch anything GPL'ed.

My personal opinion is that it's because the term 'a work' which is used liberally in GPL is a legal term and can potentially be interpreted quite broadly. This means that we have to ensure - every time - that what we do does not constitute 'a work' which derives from GPL code - in the legal sense - if we do not want to distribute the source code that we create.

With BSD we don't have to go through that process because it will not result in us losing control over our own software. We just need to stick a disclaimer in a license file and we're done.

This is probably gonna be a controversial view but my experience is this as well: Deploying GPL code is a legal process. Deploying BSD is a development process.

We spent thousands of dollars on legal advice when deploying GPL. In the end it was largely as we expected it to be: No significant action was needed beyond releasing the code to the components that we already got for free, with the minor modifications we had made. But we had to be sure before we committed to using GPL code.

Today, we have a blanket "yes you can" policy for BSD code while GPL is still on a case by case basis.

This could potentially be interesting in space. To be able to bring up repair instructions etc. on the display during a spacewalk might have applications.

Thank you for the clarification.

Does a similar video exist from the "Savings drive the economy" point of view?

Thank you! I've been looking for this video for quite a while!

It's a fantastic video for explanation for how the economy actually works.

I live in Denmark where we have had phonebased money transfers for years now (since around 2013 I believe). I've used splitwise for tracking purchases at a festival where whoever had money on them would buy beer or food and we would just track it in a group budget.

Since you didn't have cash transactions when adding you don't need too much security so there's lower friction. Further you reduce the amounts of transactions going on, while still retaining decently detailed logs. It also gave the option of solving things with cash when splitting with people from abroad who may not have the same access to easy money transfer.

Just to add some perspective.

I'll check out pocketsmith - it does sound kind of cool and I'm looking at the possibility of merging my finances with my partner soon-ish.

We did that - paying existing businesses to move out as we grew. Took over one floor. Took over the next. And the next. And the next. Ran out of floors. Then the offices started filling up more and more. And more.

Top management started looking at more space a long time ago but it's hard to come by because we're smack in the middle of downtown in major city and a lot of the people working here are really enjoying the easy access to public transportation and general life of the city. Location was part of the reason I accepted the job myself.

We just found some additional offices though, so all is well again :)

I can't wait to get my hands on one of these. If they work out as I expect them to I could see my company buying several 100 of these a year.

We're maybe 50-100 Delphi developers and most of us can't wait to jump to C#.

To each his own :)

I'm working on a system which some decently advanced functionality booting a linux 3.14 kernel on an ARM. Currently I'm getting around ~5 seconds, from turning the power on to having the system fully loaded and ready.

I could possibly get it lower but it meets spec and any additional shaving off would probably require plenty of work while sacrificing debug-ability etc. so for now I'm fine where it is :)

Perhaps Apple will launch a thunderbolt-to-thunderbolt adapter to make it work.