The author seems to be describing what happens when one's primary relationship with music is one of consumption. It is easy (for me at least) to find new music when you are looking for inspiration in your own practice of making music. Most people don't make music though so I'd imagine it's easy to get stuck in that rut.
Somewhat related: if someone whose technical proficiency you don't hold in high regard needs to perform a limited number of administrative actions on a network-connected Linux machine (like restarting a specific service or installing updates), there's OliveTin. You pre-program it with the list of actions you need by writing a small yaml config, and it builds a simple web interface which the person in question can use to solve simple problems without calling you all the time.
I like the interactive setup. I think this is solid but if you want something even faster and easier to use, try my project localias [0]. The parent project, lcl.host, has some annoying restrictions:
> This CA has some restrictions though: it can only issue certificates for subdomains of lcl.host and localhost, but that’s all you need for local development.
Localias, on the other hand, lets you use any custom domain you'd like. And if you use a domain ending in .local, it will broadcast over mDNS so that you can easily connect to that server from any other device on your wifi network (like your phone.)
Localias also allows you to share your configuration with your entire development team by committing a .localias.yaml file to the root of your git repo. This makes sharing links with each other super convenient.
Always nice to see another competitor in the space; if you're interested in this, please check out Localias as well!
Also, if you are not fighting a war and your workplace is so toxic that you have to take military grade advice on stress reduction then you should look for a new job.
the advantage of that is that it's all on-demand. no need to set up sonarr/radarr.
Just set up a bunch of trackers to search from and pick from them on demand.
There is perhaps no greater example of a cargo-culted non-optimization than the choice of Alpine as a base image. This has cumulatively wasted millions of hours of developer time. And why? To reduce the base image size.
Image layers are cached and shared! If you have one image based on Ubuntu in your stack, you may as well base them all on Ubuntu, because you only need to download (and store!) the common base image once. And if you're such a purist that you've avoided anything but Alpine base images, what have you actually gained? Your deploy time is slightly faster? Your first cold boot is slightly faster? Outside of a few serverless use-cases, this is basically meaningless and almost never a real bottleneck (and even for serverless, there is probably some level of image caching across boots).
Meanwhile what did you give up? You opted out of the most well-tested and maintained versions of binaries, and forced all software in your image to link with musl instead of glibc. Congratulations on creating an ongoing headache for yourself. You've increased maintenance costs and probably even decreased security by preferring a less-audited codebase.
I suppose one positive side-effect of the Alpine cargo-cult is that some of its more technically-inclined adherents at least contributed back to projects to improve their cross-compilation toolchains. But otherwise, it's just been a huge waste of time for pretty much everybody.
Reporting from a budget Android Tablet with Firefox, the response times aren't exactly instantaneous but aren't any different than running full LAMP on a reasonable cloud instance or VPS which is surprising to say the least.
Also imagine the software layers at play here. Whole PHP Interpreter plus whole thousands of lines from WordPress codebase plus SQLite.
Really cool tech behind this demo! I wish I could see the realtime php error/warning log (configured to log everything, of course); it would be interesting to see how perfect this simulator is, especially with the SQLite db rewrite.
It's also awesome how easy it is to use this to test out a plugin (or a theme) - you just need to add &plugin=plugin-slug-from-dir where the slug matches the plugin's WordPress.org url and it'll be automatically downloaded and added to the sandbox!
The full query api used to configure the sandbox (tech and loaded env) is documented here [0].
Now you have to build or configure a system for spinning those up and down at the command of anonymous visitors to your website. Or eat the cost of running a whole bunch of them all the time. And test that system. And monitor it. And secure it (and no matter how well you do that, you're now exposed to a wider set of risks than you were if you hadn't built this thing). And do maintenance development as dumb crap happens under & around you ("fucking [vendor] API broke on us again, with what was allegedly just a bugfix update, that they rolled out at local midnight on a Saturday without warning..."). And have another thing to look at & talk about in budgeting discussions and spending audits.
Yes, of course you can do it, and the cost of running it may be low, but the cost of bandwidth transfer to send the files to browsers so they can run these instead is probably a lot lower, and saves 100%[1] of that initial and ongoing development & operational spending. There's a largish complexity cost to the whole thing, that's all but completely absent if you run it in the browser instead.
The raw cost of running ephemeral VMs isn't the meat of the expenses I meant.
[1, edit] OK, not 100% exactly because they did have to develop this thing the link is about, but that's also a thing that can be used for other stuff, too, not just yet another way to press a button and spin up a cheap VM running Wordpress—this is a unique product, potentially, with many uses, one application of which happens to be filling the role of providing live demos in Automattic's theme/plugin marketplace.
Where the author made a mistake was in trying to make "what the market wants" rather than just making stuff he/she actually wanted to make and trying to see if it was possible to make money from it. If you try to make "what the market wants" rather than what you want, you're going to make garbage and further saturate a market that is already filled with garbage that was designed to cash in on "what the market wants". And you're not going to be good at it because you're not a large corporation that has perfected a soulless formula so your work is just going to be a worse version of what the large corporations are doing (soon that stuff will probably be produced by AI rather than humans).
You don't turn a creative field into a career or a business until you know that what you want to make is going to be marketable or you are independently wealthy and don't need an income to live. And once you're successful in a creative field, resist the urge to pay attention to marketing data.
A creative who doesn't have the backing of a large corporation needs to lead (i.e. innovate, challenge conventions, etc.) not follow. That's because you can either be better, worse or different than the competition. If you're not different and you have a smaller budget, you will inevitably be worse. That applies to startups and even incumbent underdogs in any line of business.
Most of the issues you raise vary quite a bit from one location to the next. For example visas depend on (a) the country you have a passport from, (b) the rules of the destination country, which will probably have multiple visas available with different requirements, (c) how long you need/want to stay. Every country (and sometimes every bank or even branch) has its own rules for opening accounts -- sometimes easy, sometimes not, and usually not necessary if you only intend to stay for a short time.
Health care access and costs also vary widely depending on where you go, what kind of insurance you have, how much you can spend, etc. Multiple companies offer short-term travel insurance geared to nomads, and multiple companies offer expat policies with longer and usually better coverage (CIGNA, Aetna, etc.). US medical insurance generally not accepted outside of the US (but find out). Other national health insurance may or may not cover citizens outside the home country, you have to research that.
Taxes depend on your country of nationality (where you have a passport from) and the destination country. In general people traveling on tourist visas don't pay income taxes in the countries they visit (because they are not legally allowed to work there), but increasingly countries offer remote worker visas that may include paying local taxes. Most countries tax their citizens based on time spent in the home country, but the US (almost uniquely in the world) taxes US citizens regardless of where they live, and on all income regardless of source. In my experience most nomads don't pay taxes in their destination countries, and only worry about taxes imposed by their home country. Taxation of expats and nomads changes as countries either try to attract or crack down on remote workers, you have to research and maybe get professional advice if you have tax questions.
Remote workers with full-time jobs have to either inform their employer, or try to hide their remote location from their employer. Employees working in another country, legally or illegally, can present tax and labor law compliance problems to the employer. Some companies cannot permit employees to work from foreign countries for compliance, privacy, or other legal and regulatory reasons. Don't put your employer in a bad position by deceiving them, that could cause a lot of trouble for you.
Nomads overcome the challenges by preparing in advance as much as possible, doing the research, and learning to adapt and figure things out. Inflexible and judgmental people who think the world should work the way they want it to don't succeed as digital nomads. Those who can adapt, adjust, and not get overwhelmed by bureaucracy and cultural differences succeed.
While remote work/nomading is always new to people who haven't done it, or just started, the issues are fairly well understood and written about at this point. NomadList, for example, has free information for many destinations, and an active community of nomads and expats who can answer questions. Reddit used to have a lively digital nomad forum, I haven't looked recently. No matter what you read in a blog or see in a video or get told in a forum, do your own research so you aren't stuck with bad information at some foreign immigration office, or your health insurance doesn't get accepted, or your bank blocks your debit card.
I think it is a good mindset to have. We must all assume that software is an imperfect thing done by imperfect beings. Even celebrate it.
On this particular case, I recommend concentrating not on the fact that there was a bug, but on the fact that the code written so many years ago is still relevant for someone today. Focus on that. Try to make something that someone will find a bug in 30 years from now.
I loved the video, I love this type of analysis of bugs and glitches. This comment, however, just makes me nervous. It's like my innermost worry.
I spend so much time trying to do a good job which I can be proud of and yet I always know there are bugs and I just hope not too many players notice and get annoyed by them.
And here we are, pointing out poorly written code in practically ancient software and attributing it to one particular programmer. Of course, Carmack has more than shown his worth throughout his career. But I dread the thought of a forum post pointing out mistakes I've made at work like this.
It's part of why it took me so long to dare publish articles about fun stuff I've done at work.
> ...He wanted to wean Italy off of foreign wheat imports, which were becoming increasingly difficult to acquire amidst international sanctions and a suffering domestic economy. Rice grew well in Northern Italy, so Mussolini sent free rice samples throughout the country and bombarded Italians with pro-rice propaganda.
How did pasta get so popular if they had to import the wheat? Seems they cannot produce enough for the whole population without imports even now, I would think that would make it expensive over staples thay they can grow themselves.
Poplar is an also-ran (from that time frame). Normally I prefer to concentrate on ideas (of which there are a few in the link below) rather than people ... but in this case, for context, it's worth noting the authors:
For search, abandon Google, not hope. All ye should enter here: https://kagi.com
// as a kagi user, i'd
(a) imagine this as a lens at the simplest; just pick text-davinci-003, tokens 3000 to leave room for prompt, temp 0.7, freq 1 - 1.5, presence 0.5, and instead of best of 3 or 5 show repeated calls as if 3 - 5 unique results
(b) imagine a richer implementation that summarizes other articles on first SERP, then collates and summarizes those (with the compare/contrast structured synthesis GPT-3 does well when POVs differ), and shows the final rollup summary above the individual summaries, in the right hand column
// would also be OK connecting it to my OpenAI token so I'm paying, not you. having done the math, it's nominal cost if not the default mode.
> This left a lot wondering what exactly was going on with all those engineers and made it seem like it was all just bloat.
I was partly expecting the rest of the article to explain to me why exactly it wasn't just bloat. But it goes on talking about this 1~3-person cache SRE team that built solid infra automation that's really resilient to both hardware and software failures. If anything, the article might actually persuade me that it was all bloat.
I use Mega Sync. It's the best service I've ever used for a "Dropbox" solution. Has support for every OS and mobile imaginable, plus web client is good. It also has a terminal application in which you can set up a WebDAV server, etc. etc. and really "get behind the wheel" if you want. If you don't, the device applications are great! Too many features to list. oh, and it's cheap! I keep everything in the default folders on a Mac / Linux fresh install (documents, music, videos, templates etc.) and sync the whole thing across computers except for desktop folder and downloads folder.
My mailbox.org account came with a few GB of cloud storage. I'll put encrypted documents on there (like tax return) because it's soo easy to encrypt / decrypt on a browser with your GPG key with their web application.
I use Mac devices (iPhone, Mac book) and have a Linux workstation.
> It took a minute to summon the picture on the latest and greatest iPhone 14 Pro, uses about 2GiB in-app memory, and requires you to download about 2GiB data to get started. Even though the app itself is rock solid, given these requirements, I would probably call it barely usable.
also
> Even if it took a minute to paint one image, now my Camera Roll is filled with drawings from this app. It is an addictive endeavor. More than that, I am getting better at it. If the face is cropped, now I know how to use the inpainting model to fill it in. If the inpainting model doesn’t do its job, you can always use a paint brush to paint it over and do an image-to-image generation again focused in that area.
Seems very worth a try. I'm downloading the model right now, it's going a bit slow, ~2MB/s.
Zero. Apple tries really hard to pretend they own the relationship between the user and the app developer, when in reality they do nothing to deserve it. Most app developers, Telegram included, treat the app store as a nuisance, pain-in-the-butt of an obstacle they have to clear to have presence on iOS devices. It provides negative value to them. All the discovery features are irrelevant to them. They do their own marketing and could as well have done their own distribution if Apple allowed sideloading.
Thanks for the shoutout.
I am the author of Bruno :)
A unique things that seperates bruno from the rest is that it is a "local first" api client.
The collections get stored as folders and files on your local files system (imagine git repo), thereby allowing the developers to use the version control of their choice.
Yeah, I could see that even outside of the context of the Cassandra virtual nodes primitives.
These could be K8s nodes for example, that don't make full utilization of the underlying VM, which would completely make sense at APPL scale.
For some background to other HN users out there, "virtual" nodes refer to logical nodes in distributed database software where # of virtual nodes >= physical nodes. This means if the size of data passes a certain threshold, physical nodes can redistribute the virtual nodes, reducing the amount of data shuffled across physical nodes (as opposed to a naive hash function that mods a key by a fixed number and requires all nodes to reshuffle data when a new node is added).
Newsletter: A German plushie store (Steiff) and some kind of wellness place. 2 democratic congressmen.
In all cases it’s the same, I mark them as spam and block them.