This isn't an unheard-of practice in the software world. BSD has often touted itself as the most secure *NIX-like system on the market today. When someone files a CVE, the developers use it as an excuse to powwow, crush the bug or vuln, and then continue claiming to be best-in-breed.
And yes, that's not necessarily the de-facto behavior of a lot of developers, unfortunately. Projects like Flatpak have hundreds of open issues and vulns, with only a handful of developers actually dedicated to working on it. These people often prioritize features over fixes, and they reap what they sow for it.
This is a really bizarre comment to make, considering BSD has no equivalent to flatpak. Flatpak might only have a handful of developers, on BSD you get nobody trying to fix application-level sandboxing at all. Unless I missed something and there's a new BSD project being worked on here, but I haven't heard anything.
They're both security-oriented, open-source projects with limited numbers of contributors. I'm comparing the way they handle their priorities, and moreover just trying to tie it back to how claiming to be perfectly secure is a pretty regular occurrence. It's not an apples-to-apples comparison, but it doesn't have to be for the sake of this example.
Rich is the low level part, for list select or viewports, you need the high level lib from the same author: textual (https://github.com/willmcgugan/textual).
I wrote an INI parser that has numerical, boolean, timestamp, MAC address, and IP address types ;) "advantages" of not having a spec!
Seriously: for application-specific config files, the lack of a formal spec can be kind of a nice thing. You can design your parser to the exact needs of your program, with data types that makes sense for your use case. Throw together a formal grammar for use in regression testing, and you're all set.
Obviously a formal spec is essential for data interchange, but that's why JSON exists. To me, YAML is in a gray area that doesn't need to exist. The same thing goes for TOML, but to a far lesser extent.
Everything gets serialized to a string of bytes. The point is that you can fail at parsing when the value doesn't make sense, rather than failing at some point in the future when you decide to use the value and it doesn't make sense. And if you have a defined schema, you can have your editor validate it against the schema when saving, so you don't accidentally have "FILENOTFOUND" in a Boolean.
> Honestly, I think a good configuration library should be more than a spec, it should come with a library that handles parsing/validation
You just described CUELang.
The type system allows to define a schema as well as the data, in the same file, or in 2 separate ones. Then you can call either a cli tool (that works on linux, windows or mac) or use the Go lib (or bind to it).
For compat, cue can import and export to yaml, json and protobuf, as well as validate them.
Exactly. So if I'm going to learn/use one of them, there's no clear winner, really. Both also seem to also have about the same amount of adoption (zero?).
I quite like CUELang (https://cuelang.org/), although it not yet widely supported.
It has a good balance between expressivity and readability, it got enough logic to be useful, but not so much it begs for abuses, it can import/export to yaml and json and features an elegant type system which lets you define both the schema and the data itself.
> if there's a sudden influx of thousands of users
A $10 VPS will manage thousands of users fine for most CRUD apps. You don't need tons of VM.
You can always make it a... $20 VPS to have some margin if you fear HN hug of death.
You won't get a CDN close to the user or automatic backup, but that's really fine for the immense majority of projects.
It takes one hour to setup a VPS with nginx, python/node/ruby and postgres. Then it mostly runs on its own for years: no coldstart problem, no kubs to manage.
I get the benefit of the cloud at scale, but for thousands of users, it seems really overkill.
It depends on what the code is actually doing, but you're not wrong in most cases, especially the HN hug of death. I host all of my stuff on cheap VPS servers for example.
Some tasks, though, are just terribly slow. For example, crawling a webpage and taking a screenshot of it sounds incredibly easy but turns out to involve a lot of resource-intensive moving parts. The most common solution I see involves running Chrome in a container and taking a screenshot. That kind of code can easily overwhelm even a moderately expensive VPS with just a few clients. On the other hand, most CRUD stuff and frontend-heavy applications would run fine even off a modern Raspberry Pi.
You can't just let something run, though, because you need to manage system updates. It's something you can easily forget if you have tons of other stuff to do, so the laziness factor also helps defend the *aaS setup.
I don't like serverless, I think it's the next step in more wasteful programming by people who can't or don't want to understand the systems underlying their code. We're at the point where shipping an entire operating system along with an application has somehow become the norm, and I don't like the fact that eventually I too will need to learn this serverless crap.
Indeed, things like video encoding, machine learning, graph traversal, etc, can be pretty expensive.
But then again, our tooling are so powerful these days you can get away with a lot. Timeseries ? Clickhouse is your friends. Need geo calculations ? PostGis is here. Need to extract frames from a video ? ffmpeg will do that in a few cpu cycles. Data analysis ? Say hello to pandas. Validation, caching, expiration, encryption, workflow, pub/sub, logging, reporting... We have amazing solutions for everything that will let you scale up to the millions of users for few hundred dollars.
In your example with the screenshots, one can imagine putting them in a queue (5 minutes setup with python-rq + redis) or even more low tech, a cron, and suddenly your VPS can take one screenshot every 2 seconds, which is 43200 in a day. That's a lot of screenshots.
Your client need the screenshot immediately ? The browser can take a screenshot from JS with html2canvas.
Sometimes it feels we are using $TECH because there is a whole class of devs that can't find solutions to problems:
- don't want to think about your data structure ? Put everything in no sql.
- don't want to think about your deployment ? Put everything in a container.
- don't want to think about your algo ? Put everything in the cloud.
Of course, in the end, you still have to think about all that no matter the tool you use. You just moved the cost somewhere else, usually paying much, much more later.
In fact, even most of the stuff I get paid to do using Django could be done cheaper with wordpress. I'm already overkilling it.
I think the problem is in a general overcomplexity, ambiguity, configuration overflexibility and lack of reliability with LAMP or Node or Python or GNU/Linux installations.
Today I just can’t make a guarantee for a fresh Ubuntu LTS instance that it will run a 15-line pure C or sh code as I would intend to outside of my attendance, regardless of how easy the requirements or the SLA might be.
As much as I hate serverless or easy scripting language trends, they do the job and do it well.
It probably depends a lot on what the code is doing . I've seen systems with multiple services inside and a couple of them had to do db calls and could not be cached. You can easily end up with 10-30 servers. Also, the cheap versions may not have enough cpu or memory for all systems.
In this case the serverless versions may be better, easier or cheaper. We did not use Python or Ruby by the way. I still think Python is a bad choice for most systems.
The red numbers did seem like stretching it too far, but I actually think the original construction is quite elegant. Taking the number with more dots doesn’t seem like any more mental overhead than mentally adding the values on two normal dice.
Just to further complicate things.... native English speakers often use "dice" as the singular i.e. instead of "die". While technically incorrect, it's very common, probably more common than the "correct' form.
The plural is "dice" and unfortunately "dices" is definitely incorrect :-)
I’ve even heard people use “die” as both the singular and plural! It’s the only singular/plural pair I know of where 3 of the 4 permutations show up in common parlance. I’ll be thrilled if I ever hear someone use dice as sing. and die as pl.
From the OED: "As in pence, the plural s retains its original breath sound, probably because these words were not felt as ordinary plurals, but as collective words".
The main question is, what would be the source of the bubble?
Is it cheap capital? Fraudulent bank practices? Or is it because people wanted more space during lockdowns while having the sense of financial stability?
If the demand increased while supply stayed constant, the price increase is not a bubble. I waited for "the bubble to burst" for years before realizing there likely is no bubble where I am from. Housing's just expensive.
My tip is "distrust against the future value of the currency". Bricks do depreciate as well, but not massively.
The bond buying programs of the ECB are pretty expensive already, and the Green New Deal will be mostly implemented on credit. And Europe is already quite deep in debt. So is the USA, but the USA can at least derive some strength from the dollar being the world reserve currency, with no clear challenger in view.
Because tons of professions, small business, workers laid off, etc suffered from the lockdowns, so there was not exactly clear that "people had more money to spend".
The markets are not invididuals, if we're talking about stock markets. And in Europe they don't represent most of the population as asset holders or anything like that.
Case in point for France:
"There was an 8.3% decrease in France’s economy in 2020, and the country has not seen a recession to this extent since World War II. For example, France’s travel and tourism sector’s contribution to the French economy decreased by 48.8% due to travel restrictions. As a result, that sector alone lost 193,000 jobs. (...) Before the pandemic, 9.3 million people lived below the 1,063-euros-per-month poverty line in France. Those who were poor had little opportunity to improve their lives, especially during the pandemic when unemployment rates reached a two-year high. As a result, retail workers, artisans and self-employed people were among those the pandemic most affected. Further, the number of French people in poverty has significantly increased to more than 1 million people during the pandemic. (...)"
>As a concrete example, bank account deposits in the UK rose 10% during COVID.
That's one disconnect. Most people don't have bank account deposits (or don't have any to write home about). That's apparently true for the US too...
>areful, the French measure of “poverty” is a percentage of the median income. It’s more an indicator of inequality than anything else
It does say "below the 1,063-euros-per-month poverty line in France" which whether it was calculated with the median income in mind or not, it's quite fine as a poverty measure, not just inequality (that's like making less than $12K/year, or if we adjust for cosr of life, less than $18K/year or so).
1) being a fixed percentage of a median, any variation in the median will change the “poverty rate” without it necessarily meaning anything. If the minimum wage increases by 100 euros, the poverty rate will actually increase because the median income will go up and more people will come under X% of it
2) you can’t really compare income across countries. 1000 euros a month means you will receive social housing or subsidies for private rental. It means neither yourself nor your children will pay for any state services (school, school meals, health, swimming pool etc, public transport etc). I’d far far prefer to be on 1k in France than 2k in the US
>2) you can’t really compare income across countries.
As a close by European whose been to France many times and have friends there, I can assure you 1000 euros a month doesn't by you much in France. Not sure if it corresponds exactly to $18-20K year, but it's not far.
That said, of course, being someone making 1K in France is better than 2K in the US -- regarding education, health, and several other aspects....
Yes. That’s clearly what happened. But lots of people, myself included, expected prices to go down. The early pandemic was marked by a market meltdown and a shutdown of the timber and housing industry as analysts expected a drastic slowdown in home buying and building. It was perfectly reasonable at the time to assume (or hope!) that house prices were going to fall, and let's not brow beat people over that.
Yeah, similar event happened to the car industry. Analysts and factories forecasted dramatic slowdown in sales, so are rental car companies. Yet after the reduction in investments happened, it turned out consumers in COVID prefer to buy additional cars, or rent to go to smaller towns. Cue pandemonium. (And the supply chain shortages of chips)
To be fair, if COVID happened anytime before broadband is available to homes, the analyses wouldn't miss. Novel pandemic, novel technologies, novel situations all around.
In the UK, people who suffered were low wage, casual workers such as hospitality staff- typically not people who were in the house buying market to begin with.
Public sector workers and corporate employees tended to fair well because they were 'working from home' and not paying a siginificant part of their income on getting to the office and back.
Factor in, also, much less properties available. I was looking for a house at the time and anything that came onto the market was getting snapped up in no time at all. This lack of supply soon translated into increasing asking prices.
Except that they’re not driving to work, they’re not eating at the cantine/restaurant at lunchtime, they’re not going on holiday, they’re not going out in the evening…
I've noticed that the covid crisis has resulted in steady or even growing home purchases, many of them as second homes. In the US there was a lot of talk in 2021 of those who had not lost their jobs sitting on more liquidity than ever before, so I'd assume it's many of these people who jumping into the housing market.
Interest rates fell dramatically, government stimulus/cash transfers were far in excess of any lost wages, fewer people wanted to list houses and do showings due to covid.