Depends on how quick the swap takes. If a normal charge would take 20 minutes and you’re doing a bathroom/food break anyway then it’s basically no extra time. If you need to stand next to a battery swap for a few minutes and move when it’s done then it’s extra.
EVs are weird. Certain usage patterns mean less time waiting than ICE vehicles.
That's the entire idea... normal charging for day-to-day ... swap battery for roadtrips.
The swapstations are ~200km's apart on the motorway corridors.
Nationalistic swipes are not welcome here, regardless of which nations you have a problem with. We ban accounts that post like this, so please don't do it again.
The last couple of years I have been working hard at not directing my animosity towards the Russian state against Russian people. Post like yours makes that much harder. Almost no other people will glorify their past and current crimes like Russians do.
Just writing in case some reader wonders why the downvotes.
Estonia was independent before the second world war and was doing very well. After the second world war until the nineties it was under Soviet occupation. During the occupation, there were mass deportations to Siberia, socialization of property, prevention of travel, prevention of free information and prevention of free enterprise and all those things. Until Estonia became independent again. The economic growth has been rapid since.
He is one of those Russian trolls who roams around HN telling that the slaves brought to the Americans should be thankful for the free trip they got. Except since they work on a different historic context, their vile nature gets lost on most readers.
Pre-WWII Estonia, Latvia and Lithuania were quite well developed small countries in Europe. Not on par with industrial powerhouses like the UK, but not the most undeveloped parts of Europe either. Estonia is a particularly notable example, since it shares lots of traits with Finland, comparing them is almost like a twins study. In 1938, Estonian and Finnish GDP per capita were very close, 3771 and 3589 dollars respectively.[1] Both were invaded by the USSR in 1939/40. Finland lost territory, but successfully fought Russians off and remained independent. Estonia was occupied by the USSR until 1991.
By 1995, the GDP per capita of Finland was 26 271 dollars, while Estonian GDP was 3134 dollars. In 2021, the Finnish GDP per capita was 53 489 dollars, while Estonian GDP had risen to 27 943 dollars.[2][3]
That's what 50 years of Russian rule does to a country - incredible economic stagnation, and then incredible rebound as soon as Russian tanks rolled out. In early 1990s, the average monthly wage in Estonia was 37 dollars. In 2023, it is 1800 dollars.
Russian trolls love to say how they "built the infrastructure", but they fail to mention that the natural pace of development would've been a much faster, like it is now.
And speaking of that "infrastructure", to a large degree it consisted of extremely polluting factories that produced uncompetitive garbage and went bankrupt as soon as free trade with rest of the world opened up. A great example of their "infrastructure" has been immortalized in Tarkovsky's sci-fi movie Stalker. The polluted wastelands with foaming rivers and white ebbs falling down like snow in summer weren't special effects. That was toxic waste from an upstream chemical plant that directed its waste unfiltered into a nearby river. Several crew members, including Tarkovsky himself, fell ill and died due to the poisioning received there.[4] Cleanup of such "infrastructure" continues to this day, 30 years later.
Beware of Greeks bearing gifts, and Russians building infrastructure.
I'm lithuanian and this is false propaganda, Lithuania was independant before Rusian occupation back before the world wars and in between the World Wars, unless you consider Stalin and Hitler splitting lands as "purchasing".
Well it's not exactly secure by default. I was deploying an app to a new server and some bot grabbed my .env file before I finished the Apache config.
Ultimately it's my own stupidity, but you don't have to worry about that with most other languages
You shouldn't deploy .env files to production. You should set the actual environment variables on production. .env files are intended for convenience on non-prod systems.
Agreed, but server frameworks shouldn't easily enable a foot gun that allows bots to have disk access to your host. Instead, only explicitly defined routes or resource files should be available.
If I had to guess, this person committed their .env file in some repo and pushed that up, and that become available because the server was misconfigured.
For other servers (such as, say, Jetty), config files like that won't get exposed like that unless you're very obviously placing your config files in a public resource folder.
Yes but that’s a framework specific issue. And usually your documentroot would point to a directory below that which holds .env. Oh the memories of apache and php.
The mere concept of a "document root" is a problem though and a major footgun if you don't know what you're doing.
Every other language acts as its own web server which wouldn't even be capable of serving files even if you tried; the only thing it does is respond to web routes defined by the application.
This eliminates a whole chunk of security issues, from the one described above to malicious file uploads (PHP is probably the only language where a malicious file upload leads to RCE by default - other languages could happily accept and serve the malicious file back but wouldn't execute it).
> The mere concept of a "document root" is a problem though and a major footgun if you don't know what you're doing.
A non issue though after 2-3 days of working with this approach. All modern PHP frameworks have a so called front controller (an index.php file) that loads what it requires from ../ after, ideally, properly validating the request to avoid issues.
Some frameworks in the old days of PHP relied on .htaccess files to restrict access to unwanted files. Properly implemented frameworks would load everything from a directory above the documentroot to avoid these issues.
That has nothing to do with PHP. If you have .env files in your document root PHP didn't put them there or require them. Every web site back-end can expose .git directories or .env files if not configured correctly -- that has nothing to do with PHP except that way more people use PHP out of the box and don't know about these issues or how to fix them. That's analogous to way more teenagers crashing cars than more experienced drivers, but that has nothing to do with the particular cars.
I've just used this in Malaysia, they have a card called Touch n Go that is very widely accepted.
You can load up the card using cash terminals or via a smartphone app with NFC, you can use that to check the balance as well
I have a very excellent SSD which I removed from that system because I am certain that the Windows installer would fuck it up, and I did not want the hassle of trying to fix it. So I pulled it out of the box to keep it from harm, and the only media I had at hand at that moment was a WD SATA HDD. I thought it would be slow, not kill-me-now slow.
I do not "use an HDD" of course. It was improvisational.
The same reason anyone has always used a HDD? … they're dirt cheap, compared to SSDs.
I'd consider hybrid being the best cost option, with a small SSD backing frequently used data, like the OS. But there's more complexity in that setup. I'm also a Linux user, and boot times don't bother me.
If you need very large (4TB+ drives) maybe, but 1-2TB SSDs are so cheap nowadays. 2TB SSDs today are cheaper than 2TB HHDs from 10 years ago, and the price discrepancy is quite narrow unless you're looking at 4TB+ drives.
I don't even bother looking at HHDs for my own computers anymore unless I need bulk storage for videos or something.
Yes, HDDs are slower than SSDs. If that axis matters to you, you'd use an SSD, particularly NVMe. (Which is sort of implied by the hybrid setup I suggest.) If storage capacity matters, HDDs. You can see this reflected in market prices, though it does look like SSDs are surprisingly cheap these days, comparatively. Historically this has not been the case. (I wonder if economies of scale are now working against HDDs suddenly, or what? There's no reason for them to cost the same or more than an SSD — the market would collapse. Although I swear market pricing for many components hasn't made a lot of sense, recently… i.e., RAM has seemed horrendously expensive.)
There's some sort of big SSD price drop in the past 3 months. I dunno what that's about, but I did upgrade a machine, so that's nice.
There does definitely seem to be a pricing mechanic in that hard drives never really scaled down in minimum unit cost; the basic parts of a hard drive still cost real money, so if you can do 2TB per platter, and a top of the line drive has 10 platters, a single platter 2TB drive costs a lot more than 10% of the top of the line drive. OTOH, flash controllers aren't that expensive and/or the cost of the controller scales with the capacity, so SSD prices tend to be more linear with capacity.
If you need a lot of space, $/B means a lot, but if you just need an ample amount of space, $/device is more important, and SSD drives have hit the point where an ample amount of space is available for less than any hard drive.
The most efficient cost option is to have one cheap SSD for booting and a handful of apps that need the speed and then using a HDD for storage. Been that way for 10+ years
The slowness you see with NVME isn't in boot anymore - instead it's in BIOS. As memory times get faster, it takes longer for the motherboard to train to hit those XMP targets, especially with memory still super far away from the CPU. For me, rebooting has ~20 seconds of staring at a blank screen with the Motherboard doing memory training/initialization on 6000 MHz ram.
And I do professionally. I haven't seen a good interface on any of the other products. They're stuck with clunky 90's interfaces. Circuitjs is far ahead.
Circuitjs is superb for exploring electronic concepts. The quality of the simulation itself is subpar, though mostly good enough. The ability to save a circuit to a url is another thing that sets it apart, and is invaluable for communicating concepts.
