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 :)
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 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.
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.
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.
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.
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.
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.
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.
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 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.
> Do you keep your savings in your checking account?
Yes! :)
Moving coins manually between a hot and cold wallet is a hassle and what I would consider a significantly worse user experience than what exists today.
Exactly. I've made this point before: The least appealing thing about crypto to me is one of the selling points - That I can be my own bank. I don't trust myself nearly enough to be my own bank. I want to pay someone I trust to take care of that for me. I don't want hacking or forgetting a password to be something that in any way affects my holdings.
That's true in the short term, but one of them has to be the first to move. Shifting from coal to renewables does nothing for the environmental impact of cars in an all-ICE system. If we get a larger percentage of electric cars, the impact of switching to renewables will also increase.
Could it be a possibility to generate a keypair on the machine and then attempt to register itself to your webserver supplying client-name, IP and public-key. Then you would be able to see and OK any attempts to connect. Once you've OK'ed it, it would be able to authenticate and communicate normally as an authenticated device.
How often do you have outlays for another person or give someone cash?
The application can be used for any transaction. I usually use it if I've been out with some friends, then it's super easy to split the bill afterwards. Or if going shopping. Or if we share a taxi.
Before we would either settle in cash or by trying to spend approximately the same. Now everything is done this way.
I'm in the process of building a SaaS and looked briefly at Chargebee. Right now I'm trying to stay as lean as possible so I quickly wrote of Chargebee as something that would cost money.
The fact that you have a freemium tier completely changes my perspective on that. Guess I didn't spend enough time looking :)
Can't you just give a lower price at 10 yards and again at 50 yards for example? Then you solve your baked in price issue and get to offer discounts on high amounts, incentivizing buying more.
When i think master/slave i think SPI master/slave, where the slaves only do as told by the master. In which case the primary/replica relationship would not be suitable, while the master/slave relationship is descriptive of what actually goes on.
If we have one (in my view unoffensive, but that might be a cultural thing) term which adequately describes the relationship - why not use it?
I'm also still not on the docker-wagon and would like to know what I'm missing out on. Most of my stuff is python. Why is docker better than virtualenv with a requirements.txt file?
From this description it seems to solve the same issue.
I could imagine something like environment variables, but on the other hand that's something I've learned not to keep in version control, and putting it in docker would be exactly that, no?
Basically yes. But the frequency used for PWM is usually _way_ higher than what should be realistically visible to the human eye - If it was me, I'd probably use a couple of kilohertz.
Not sure how specifically it's done for OLED though.
It's funny how Google has been banging on about "just a few milliseconds of extra loadtime and your bounce-rate increases!" while in Gmail it's like they think the product is so good, people should be willing to wait 10 seconds to view their _mail_.
The reason I'm even reading this comment section is because I wanted something to do while waiting for Gmail to load.
If you're able to live with a lower consumption you should not increase it just to "not harm the economy". On the contrary I would find it unethical to increase your consumption beyond your need.
To your second point, I don't find it compelling either. First off, the FIRE way requires some amount of restraint and discipline - in many ways it's like dieting. It's good for you, but that doesn't mean people will do it - it will continue to be only a subset of people. Secondly, how would the system would adjust? What would be the driver for lower wages? The method is basically to save and invest half your income - that doesn't depend on your income. The people are still equally skilled, working equally hard during their working years. The output at their work while they work remains unchanged.
If anything it might drive wages _up_, as people would require increasingly higher compensation to stay at work, if the alternative is to live happily and safely without working.
Yeah, same thing in Denmark. When my girlfriend gave birth, we had 3 midwives assisting. When she lost what they deemed to be too much blood, they called in a doctor to take a look. Everything was fine. If she hadn't passed some specified threshold for bloodloss, we would not have seen a doctor (or a nurse, come to think of it) at all throughout the birth. Only midwives.
Looks like the ethernet is connected directly through RGMII - meaning the USB 3.0 controller is likely completely out of the picture. That would mean you can run full throttle ethernet without affecting the USB speed at all.
As someone who's always late to the party on these things (I just picked up Docker this year! Yay!) this seems like exactly what I've been missing when trying to pick up serverless.
Granted I haven't really tried building anything yet, but part of that is that I needed a way to get an overview what could even be done. This seems like a nice way to get introduced.
I feel like a lot of this is rooted in some assumptions that are not being said aloud that you may not even be aware that you have. This is no in any way an attack on you - I find this entire thing absolutely fascinating. I've seen a check twice in my life: One time and old lady tried to pay with it, when I was working as a cashier - I had to call in help, as we were no longer being trained in how to accept them. The other time, I had to get hold of one when I was studying in the US, as I had to pay some fee that was only payable by check. Took me a month and cost me $30 to convince my bank to help me with it, as they told me they weren't sure they could even do it - they hadn't done it in years.
For context, I'm from Denmark.
First of there's absolutely nothing secret about our account numbers. All they can be used for is for transferring money _to us_.
No one carries cash around. Ever. Anywhere. I have not paid anything by cash in at least... I don't know, 10 years? 15? It's mostly used as gifts. Taken out of the bank, handed over, then carried back to the bank.
Basically all banking can be done online or via app. The only time I visited my bank was in regards to my mortgage, and even most of that was handled by email. If I want to do a direct deposit / bank transfer, I can just log into my app and do it. Takes maybe 1 minute.
However these days, most private transactions are done using an app called Mobilepay. Nowadays every single person has it. It's completely free to transfer money for regular people. You can also set up a business account, which I believe may carry a fee but it's minimal (just checked, 10 cents pr transaction in the priciest tier - roughly 4 for the cheapest).
For something like a woodworking business, the way to handle business-to-business transactions, you would probably go with something like an invoice. That's usually completely automatically handled by (free )software, and would only really require the other persons email to get started. The other person receives an invoice with (for example) a direct deposit address and an amount. The transfer is free and require no setup from the payer.
Internet access is everywhere and incredibly cheap. As en example, 6 GB and 6 hours is $10 a month, unlimited data and hours is roughly $20 a month.
Check bouncing is not a thing. You can verify the payment before you deliver the service. Mobilepay payments are instant - I get a notification on my phone that I have received the money as soon as the other party finishes their transaction.
In Denmark we have a secure (government controlled) email for communicating securely with government entities and banks. It's where I receive any medical updates from my doctor and any official information from the government. I also receive my payslip, pension info etc.
It has cut down a lot on paper usage and made communicating way more efficient.
I do think there's some value in being able to tersely express your exact point to a peer.
For example "a random process" could mean "any process in existence" whereas "a stochastic process" clearly states stochastic as being a property of the process.
I however agree that things can sometimes get a bit wrapped up in sounding cool just to sound cool.
> Applications are welcome from anyone with an appropriate combination of academic achievement and industrial experience; a first degree in a related discipline may be useful, but is by no means necessary.
> Each MSc within the Software Engineering Programme is available only to part-time students; there is a separate MSc in Computer Science for full-time students.
I believe the full time study noted here is what you linked to.
Certainly is to me! I build embedded Linux devices. Our current boottime from cold-boot to fully functioning is roughly 3 seconds. I would really like to get it lower and shaving off almost half a second would be amazing.
