549 karma · joined December 9, 2014
[0]: https://www.usenix.org/system/files/conference/osdi16/osdi16...
This also has the advantage that you can use the exact same distribution that the instructions for said package mention. (If the thing you want to compile has instructions for Ubuntu 16.04 no problem just use the docker image for that)
For anything that you want to use on a regular basis, creating a nix package is pretty easy most of the time. If you only want to build a newer version of a package directly from git, you can even copy the package for the stable version and just overwrite the src in many cases.
Regarding software that works on NixOS but not on other distros I think it's usually the other way around: by testing your software on NixOS you uncover issues that would have made your software less portable (hidden dependencies, hardcoded path assumptions, ...)
Of course you can say now I mixed style with HTML but if you never intend to change style separately from HTML then why introduce the mental overhead of indirection?
Small size is needed if you want to embed this into something but for that use case it lacks easy access to io ports and other peripherals.
In the document case, it is possible to mostly keep the document semantic and apply styling via CSS. It matches the content/style separation well.
For web applications, I really like tailwind-like approaches, for multiple reasons:
* changing the style globally is probably hard anyway without adapting the HTML as well (as in the app case, often lots of other things depend on margins etc for example and you have a lot less uniformity/more special cases than in the document case)
* because there is less uniformity, the reuse aspect of the traditional content/presentation split is greatly reduced anyway
* web apps often use component based frameworks already, so you still get reusable components
I am not sure in which part of the code to look for this (is the hole punching part of the dht package?) so any pointers are appreciated
I view IPFS as a better distribution network, not a better host - in contrast to current's internet structure, if many people request the same content from me, they might only need to contact my server once and then share it between them thus reducing overall load.
So the point of IPFS is not to store content for eternity, but to provide efficient distribution of content.
But there are definitely things were Linux is hit or miss (ime):
- video drivers (integrated graphics work well for me) - integrated SD card readers
But if you don't have too fancy hardware requirements I think Linux can be OK.
* systray icons/application indicators
* newer fontconfig versions support new config options which results in fonts being broken for apps that use older versions
* I think there is some issue around glibc locales handling if you use a different glibc
* systemd/logind/... DBus apis
Those were just some external interfaces that came to my mind. I'm sure there are many more.
If you really write simple code, you should also be aware of the shortcomings of the simple approach.
<<imports>>
code you want to show
and then later define what `imports` should be.
I think mailbox.org supports custom domains and is similar in other respects.
I think for .de domains, you are required to have your personal address in WHOIS if you are not a company.
* No one can get access to Google's data * Those who can get access cannot harm you
In addition to trusting google not to be evil. What are your assumptions that lead you to that conclusion?
Or are you assuming that no matter who has access to your data, there is no one could ever do any harm to you with that data? (That's the 'I have nothing to hide' argument)