If Factorio and Civilization do a kid.

So why do we continue to perpetuate the myth of conventional current flow (CCF) when we have known for a century that current in most electrical and electronic circuits is electron flow (EF)?

alter column object type jsonb using object::jsonb;

What's wrong with a simple, feel good movie?

As has been mentioned this is a take on the Prince and the Pauper story that may not appeal to those who are into art films and like to sit around discussing and dissecting a film's philosophical nuances. If, on the other hand, you simply like a fun story, gorgeous sets, and yes, the occasional over-the-top scene, this can be a thoroughly enjoyable tale of a man who is willing to put the woman he loves ahead of himself.

There are too many people giving this 7+ stars and even 10 stars (unusual to see on IMDb) to believe the legitimacy of the number of 1-star "worst movie ever" reviews. Such paradox is simply difficult to accept as valid.

I almost didn't watch this movie due to the repetitive negative reviews here on IMDb. Usually I find reviews here fairly spot-on. But in this case I am convinced we are living in a generation of viewers who have been raised on so much schlock, sex, violence, blood and foul language that they wouldn't recognize a prime movie if it whacked them with a hammer. Either that or we have a set of the most bogus witch-hunt reviews ever.

Please, feel free to consider the negative reviews as suspect (at the very least)-- and give this film a try. The best and most valid review is your own.

I know this bug is labeled invalid and I know the devs don't want to address the issue further...but if anyone reads this I'd really like to know if there is some way *advanced* FF users can enable cross-origin downloads. I mean, c'mon, the case against allowing cross-origin downloads is built on the premise that users could unknowingly download a file from a site containing their own personal information (e.g., gmail.com) and save it using a misleading name (e.g. "30off.coupon.txt") AND THEN proceed to another malicious page where they directly go and upload that same file they just downloaded. I mean c'mon. Seriously?? Anyone who's gonna fall for that deserves to lose their personal information. I'm all for browser security, but I think a simple preference in about:config to enable cross-origin a@download is in order. Please consider. Thank you.

The Bugzilla issues don't seem to rule-out the possibility of using CORS for cross-origin download attribute support in the future, but right now using CORS headers does not do anything for the download attribute. It's possible that if other browsers start supporting the attribute, a consensus may yet be reached.

This actually is possible with JavaScript, though browser support would be spotty. You can use XHR2 to download the file from the server to the browser as a Blob, create a URL to the Blob, create an anchor with its href property and set it to that URL, set the download property to whatever filename you want it to be, and then click the link. This works in Google Chrome, but I haven't verified support in other browsers. window.URL = window.URL || window.webkitURL; var xhr = new XMLHttpRequest(), a = document.createElement('a'), file; xhr.open('GET', 'someFile', true); xhr.responseType = 'blob'; xhr.onload = function () { file = new Blob([xhr.response], { type : 'application/octet-stream' }); a.href = window.URL.createObjectURL(file); a.download = 'someName.gif'; // Set to whatever file name you want // Now just click the link you created // Note that you may have to append the a element to the body somewhere // for this to work in Firefox a.click(); }; xhr.send();

The intent of this specification and related tools is to expand the reach of development containers, allow the usage of containers by themselves or different orchestration technologies, and allow any tool to manage and create them.

The focus of the dev container specification is to describe how to enrich a container for the purposes of development, rather than acting as a multi-container orchestrator format.

and they've been focused on using Docker or Docker Compose

Context

A development container allows you to use a container as a full-featured development environment. It can be used to run an application, to separate tools, libraries, or runtimes needed for working with a codebase, and to aid in continuous integration and testing.

A GitHub Action and an Azure DevOps Task are available for running a repository's dev container in continuous integration (CI) builds. This allows you to reuse the same setup that you are using for local development to also build and test your code in CI.

Our development container teams across Microsoft and GitHub continue active development on the new Dev Container Specification, and this iteration had several exciting highlights.

Many believe that companies should give more time to employees to contribute to open source, with 79% agreeing or strongly agreeing that companies should give time during work hours to contribute.

time is listed as the biggest barrier to contributing to open source projects

while just 20% have been paid for their contributions to open source, 53% agree or strongly agree that individuals should be paid for open source contributions

At this point, you’ll want to mow your grass 3-5 times. This amounts to roughly once per week. Do this before walking on it.

Add in another two or so weeks for the grass to grow tall enough for its first mowing, at which point you have no choice but to walk over the area.

all duplicate rows are removed from the result set (one row is kept from each group of duplicates)

these two SELECT clauses are NOT equivalent, so be careful: SELECT DISTINCT(event_id, start_time) FROM ... SELECT DISTINCT event_id, start_time FROM ...

Logically, if you just want a distinct list of event_id values, what order they occur in should be irrelevant. If order does matter, then you should add the start_time to the SELECT list so that there is context for the order.

The ORDER BY clause can only be applied after the DISTINCT has been applied. Since only the fields in the SELECT statement are taken into consideration for the DISTINCT operations, those are the only fields may be used in the ORDER BY.

an alternative to Matthew's answer is using an aggregate function like MIN or MAX for the sorting: SELECT event_id FROM Rsvp GROUP BY event_id ORDER BY MIN(start_time)

I just went through a small example in my head which helped me understand why Postgres has this seemingly odd restriction on SELECT DISTINCT / ORDER BY columns.

I know this is a rather old question, but

Needing to use ruby2_keywords explicitly for delegation is unfortunate, I wish there would be a more natural way to express delegation in Ruby 2.7. Unfortunately there is not.

I once proposed to enable ruby2_keywords by default to preserve compatibility, but this was rejected.

Remove the commit from step 2. We will merge ignoring the failure. Remove the commit from the other, check it passes with the other commit now on main. Merge the other. We will trigger builds for the main branch of affected repositories to check if everything is in order. Steps 5-8 should happen continuously (e.g. one after another but within a short timespan) so that we don't leave a broken main around. It is important to triage that build process and revert if necessary.

With first-class keyword arguments in the language, we don’t have to write the boilerplate code to extract hash options. Unnecessary boilerplate code increases the opportunity for typos and bugs.

Confusingly, if the police suspect you of a crime, you can be described as a “suspicious person” and if you constantly suspect others of crimes, you can also be called “suspicious.”

It never makes sense to say “I am suspect that. . . .”

It detects bots/spiders and serves them a clean page

The shared context worked though thanks! RSpec.shared_context "perform_enqueued_jobs" do around(:each) { |example| perform_enqueued_jobs { example.run } } end RSpec.configure do |config| config.include_context "perform_enqueued_jobs" end

sew

Where around hooks shine is when you want to run an example within a block. For instance, if your database library offers a transaction method that receives a block, you can use an around to cleanly open and close the transaction around the example.

We document the order of hooks, but I don't think we document where in that order we integrate Rails helpers which makes this confusing, I do sort of think this is a bug but as we use RSpec to integrate Rails here and RSpec Core has no distinction that matches before / after teardown its sort of luck of the draw, we could possibly use prepend_after for Rails integrations which would sort of emulate these options.

1/ It fits into existing spec based testing infrastructure nicely, including running on travis, code coverage using SimpleCov, switching between generating a profile (RubyProf), a benchmark (Benchmark::IPS) or normal test run. 2/ Some of my benchmarks do have expect clauses to validate that things are working before invoking the benchmark.

At the moment my open source time is much more limited than it used to be so I haven't gotten around to it yet.

FWIW, I've changed my thinking on this a bit.

I think RSpec should provide around(:context)/around(:all). Not because of any particular use case, but simply for API consistency. It's much simpler to tell users "there are 3 kinds of hooks (before, after and around) and each can be used with any of 3 scopes (example, context and suite)". Having some kinds of hooks work with only some kinds of scopes makes the API inconsistent and forces us to add special case code to emit warnings and also write extra documentation for this fact.

That's cool, I get it, it's unpaid open source work :)

I just wanted to mention there was, IMHO, a valid use case for this. It helps add to the validity of the ticket and the design of the feature.

before(:all) do @fiber = Fiber.new do Benchmark.ips do |benchmark| @benchmark = benchmark Fiber.yield benchmark.compare! end end @fiber.resume end

I've been thinking of looking into implementing this in rspec-core, primarily to make the API more consistent (e.g. so that you can combine any scope -- example/context/suite -- with any hook type before/after/around).

In the meanwhile, my was born so I am not going to get back to this issue before a while :)

It really looks like a few lines of code — https://github.com/seanwalbran/rspec_around_all/blob/master/lib/rspec_around_all.rb — which complete the DSL and make up for those 0.1% of the cases like mine.

we routinely choose not to add or expand features we think are a bad idea, or simply that aren't in popular demand, not because we're "saving the dummies' asses" but because adding new features creates a maintenance burden upon ourselves which cannot easily be undone. Once a version of RSpec supports something its there until a next major version which could be a long time away, we have several features already that we don't recommend extensive use of (expect_any_instance_of for example, we'd recommend not using it but we know there is popular demand for it so we maintain despite the extra burden it causes) so we're understandably not keen to increase that number.

Guys, I'm sorry to revive an old discussion, and if there's a new one, point me to it please.

Now I'm puzzled by the apparently biggest obstacle to implementation of this feature: possible misuse. I love ruby community, but sometimes saving the dummies' asses goes a bit too far.

'm open to considering adding this to core but it's such a rare need (given that you're the first to ever ask for it, and I've never wanted or needed an around(:all) hook) I have a preference for keeping it in external gem if we can do so w/o hooking into rspec's internals

does the microgem I published work for your use case?

We actually already use this patch: http://myronmars.to/n/dev-blog/2012/03/building-an-around-hook-using-fibers

Sponsorship allows me to focus my efforts on open source software. I also provide professional consulting services.

As for publishing this as an actual gem on rubygems.org...I have enough open source I'm involved in all ready (or too much, as my wife would probably say) and I'm not really interested in maintaining another gem.

I’ve been looking everywhere for examples of how to use Fibers that are complicated enough to do something useful but simple enough to understand. For an older feature it’s one of the least documented.

I haven't done a lot with Fibers,so having you point out a potential use for them and then walk through it was great.

group.run(double.as_null_object)

This is an excellent opportunity to mix compost into the topsoil before sowing the seeds across the yard.

You can cover grass seed with compost, but using too much can block sunlight and oxygen from reaching the seeds during their critical growth period.

Seeds might be able to grow in topsoil without compost, but seeds can’t grow in compost without topsoil.

If you’re applying pure seed to the ground, a layer of topsoil should always be put down first rather than after.

Keep in mind that you want to integrate the grass seed with the compost with a light raking.

But in GraphQL, all types are nullable by default, and you opt into non-nullability

In other typed languages, like TypeScript, Flow, Rust, or Haskell, all types are non-nullable by default, and you opt into nullability.

Giants that prefer the hyphenated spelling—Merriam-Webster, The Chicago Manual of Style, and The New Yorker, have a good reason for doing so. E-mail is a compound noun, made out of two words—“electronic” and “mail.” The e in e-mail is an abbreviation for “electronic,” and it’s used in a lot of other words as well—e-commerce, e-learning, and e-business, for example. There are also other compound nouns formed from an abbreviation and a noun, like the H-bomb, which is short for hydrogen bomb. The general rule of hyphenation in compound words that combine a single letter (or a number) and a word is to hyphenate them. So, based on tradition, e-mail is the correct way to do it.

If you paste a message from somewhere else that spans multiple lines, you can quote that without having to manually prepend > to every line!

for parsing and converting a superset of Markdown

supports standard Markdown (with some minor modifications) and various extensions that have been made popular by the PHP Markdown Extra package and Maruku

We overload the meaning of "GFM" to mean "GitLab Flavored Markdown", which is a superset of GitHub's version. However it can cause confusion as they are not the same thing.

We should ask the PM to chime in and post it in #naming on Slack.

lationship (offset) to Coordinated Universal Time (UTC). (This is distinct from some usage in scheduling applications where a local time and location may be known, but the actual relationship to UTC may be dependent on the unknown or unknowable actions of politicians or administrators. The UTC time corresponding to 17:00 on 23rd March 2005 in New York may depend on administrative decisions about daylight savings time. This specification steers well clear of such considerations.

I'm disappointed because the image for this item is misleading. It has clearly been altered to appear that the balls/marbles that come with the set are larger than they actually are. If you look closely at the picture, you can tell that the balls were digitally edited in to the original image.I have a child who still likes to chew on toys, and only purchased this for him because it appears in the image that the balls are much too large to be a risk for choking. In actuality, they're about the size of marbles and a very high choking risk.Misrepresenting this in the photo is potentially dangerous

This may be because Ubuntu 21.04 uses Wayland by default, which restricts screen recording for "security".

The dirt will sift through underneath whereas just board shoves dirt and it piles up in front of boards.

GNU cmp compares two files byte by byte and prints the location of the first difference. We can pass the -s flag to find out if the files have the same content.

pe() { for _i;do printf "%s" "$_i";done; printf "\n"; } pl() { pe;pe "-----" ;pe "$*"; } db() { ( printf " db, ";for _i;do printf "%s" "$_i";done;printf "\n" ) >&2 ; } db() { : ; }

Some people have expressed surprise end even doubt that it could be faster to read the files twice than reading them just once. Perhaps I didn't manage to explain very clearly what I was doing. I am talking about cache pre-loading, in order to have the files in disk cache when later accessing them in a way that would be slow to do on the physical disk drive. Here is a web page where I have tried to explain more in detail, with pictures, C code and measurements.

Remember the caching. Reading two files sequentially into memory from the physical disk can be faster than reading them both in parallel, alternating between them (moving the read head back and forth). Everything you do later, with all the data cached in memory, is relatively much faster. But yes, it depends on the data, and this is an average. Two files that actually do differ in the beginning will be faster to compare byte by byte.

You should mentioned what you listed after the word try_files. Here's what I ended up using that seemed to work: try_files $uri $uri/index.html $uri.html /index.html; The /index.html at the end needs to match the fallback: 'index.html' part of your adapter-static config. Otherwise going directly to a route that doesn't have a matching file at that path -- such as any route with a dynamic param like [id] -- will result in a 404.

Here's another convenient use of try_files, as unconditional redirects to named locations. The named locations are effectively acting as subroutines, saving duplication of code.

Keep in mind static here does not refer to the content on the page! Static sites can still be reactive, communicate with APIs, etc. it just means that the website package, aka the contents of the build directory that you upload to your host, doesn’t ever change.

Both solutions to insert <hr /> a horizontal line seem insane to me. You can insert nearly anything but an actual horizontal line. pray for a solution. But no actual <hr /> I can find.

The more sensible “horizontal line” htlm= <hr /> just isn’t in the program it appears.

HTML <hr> element: The prior warning is doubly important because there is a tendency to associate the term “horizontal rule” with the HTML <hr> element. LO does not generate this HTML element, either in ODT XML or when exporting to HTML, regardless of the type of horizontal rule used. This, and the preference to use styles in deference to graphic objects may also have influenced the decision to remove the Insert > Horizontal Rule… menu option and associated gallery.

However, these implicit dependencies may cause problems when running Bazel in an airgapped environment, even if you have vendored all of your WORKSPACE dependencies. To solve that, you can prepare a distribution directory containing these dependencies on a machine with network access, and then transfer them to the airgapped environment with an offline approach.

Check it out and tell us what you think. Go ahead; we’ll be here when you get back.

Narrative documentation:

Two big cons:- Can't save in the middle of a mission, and you don't know in advance how long a mission takes. (I'm too old for long playing sessions, and my kid who likes to play this with me, is too young.)

The game has no respect for your time. Saves? Nope, doesn't have them. You have to play each level through to completion in order to move onto the next one. If it had even a save and exit feature it would change my opinion dramatically.

Next, the game -does- have saves, but the devs couldn't figure out how to serialize data mid-mission and read/write a save file. "It was technically impossible due to our decision not to do it." Again, playing your game is actually not the most important thing in my life, and I don't want to spend an hour doing most of a mission only to be called away by real life and then have to start over. I get that you're apparently licensing a black-box physics engine which doesn't give you insight into its immediate state - that shouldn't matter. If you have access to the variables in memory, which you have to do for the game to run, you can serialize those variables.

It was technically impossible due to our decision not to do it."

I could love this game so easily. First off I enjoy God Games in general; Populous used to be my first exposure and remained my favourite for a long time. Secondly, the art is funky, and the creatures all make appropriate noises. Seriously, that really adds to the amount of fun I have with a game. It's also a Goldilocks game for me -- not too simple, but also not overwhelmingly complicated, so it's just right for those times when my brain isn't necessarily at its best, but I am not ready to go to bed yet, and I want something more interesting than point-and-click, yet Civilization is way too demanding.The game has a lot of options, which I also enjoy -- you can play in story mode, where you can choose from 5 different missions, starting quite easily and ending with a real challenge. Or you can play in survival mode, with 3 different difficulty options plus complete customization. It is possible to play the game 100% peacefully, no pests, no enemies, no disasters at all, which is also something I prize when I want to relax. And you can make it unbearably hard on yourself, so there's definitely a lot of replay value here.

So why am I not recommending it? I want to! The developers generally did a pretty good job, and I like to reward that, especially with so many games on Steam that are abandonware.For one, it's aggravating that the AI is not smart enough. Mims don't seek rejuvenation in their house when they most need it, especially guardians who have nothing to do but guard the place. And yet, they don't recoup their energy easily enough, which means I have to micromanage constantly. Mims who get hurt badly don't march straight for home either, and can easily die on you ("too stupid to live" comes true). I ended up choosing a custom game with only the meekest pest at a low rate of invasion simply so I could figure out where the AI fell flat on its face, and alas there are many places. And while I can micromanage rejuvenation and attacks on pests/enemies, I cannot make my Mims cut down vegetation; I have to burn it, and the burn rate is not high enough at the start to deal with the regrowth rate. That alone wouldn't cause me to recommend against a game; I'd put up with that, because it is of course its own challenge to figure out a way to win within a game's constraints. I find methodical analysis and trial building fun in its own way.

But here's the deal breaker:You cannot save in this game. And it doesn't even warn you that it doesn't auto save; when you leave, that is it, your game is gone and you have to start over. You can't set up two different scenarios, compare them, and tweak each. If you want to spend some time carefully fine tuning your game's economy, you have to basically remain logged into it for days. Which totally distorts your hours spent, aside from taking up memory from other games you might want to play or from actual work. And if your computer crashes, it's all for naught anyway. If you build a masterpiece of Mims civilization, better screen print it and then kiss it goodbye, because there is no return to old glories.So I am sorry, but I cannot recommend it. If this doesn't bother you, by all means, I think it's well worth buying even at full price, because you can get many hours of gameplay out of it if you just don't leave the game. But for me, this is a death knell for a game; I lose all interest if I can't save my work to get back to it later.

Zimbu is an experimental programming language.  It is a very practical, no-nonsense kind of language.  It mixes the good things of many existing languages and avoids their deficiencies.  And then throws in a few brand new ideas.

No option is perfect here, but a warning seems like a decent compromise unless there's a whole bunch of other plugins that break

Easy fix, but your argument cuts both ways: Many people update Vim regularly alongside their distro, but never bother to manually update their plugins.

If you had solved this any faster, it would have been in the past. Maybe going forward you can start helping us before we ask? vim-oracle plugin?

I watched some of it to help me track it down. It's offensively bad with no redeeming qualities. Shame on Netflix for streaming it.

The developer purchased Survival Engine - Crafting Building Farming by Indie Marc from the Unity store to build his game.This in itself wouldn't be a problem - that's what assets are made for, after all - but the amount of customization they put in equals to almost zero.

If you have a use case not supported by the existing public APIs, please ask and we'll be glad to add an API for you or make an existing private API public.

DatabaseCleaner.strategy = :truncation, {:except => %w[spatial_ref_sys]}

I spent some time trying to figure out why I was receiving: GetProj4StringSPI: Cannot find SRID (4326) in spatial_ref_sys From my tests. Of course SELECT * FROM spatial_ref_sys returned 0 rows.

IF NOT EXISTS (SELECT * FROM spatial_ref_sys) THEN ⋮ ANALYZE spatial_ref_sys;

depending on how the role is set up

Hi Vic, I know this post is old but was hoping to get some help here.

alter database mydb set search_path = "$user", public, postgis

Wow. I did not imagine it would be this convoluted.

The lateral keyword allows us to access columns after the FROM statement, and reference these columns "earlier" in the query ("earlier" meaning "written higher in the query").

The difference between a non- lateral and a lateral join lies in whether you can look to the left hand table's row.

The comma ( , ) in the FROM clause is short notation for CROSS JOIN . LATERAL is assumed automatically for table functions.

LEFT OUTER JOIN First, an inner join is performed. Then, for each row in T1 that does not satisfy the join condition with any row in T2, a joined row is added with null values in columns of T2. Thus, the joined table always has at least one row for each row in T1.

This latter equivalence does not hold exactly when more than two tables appear, because JOIN binds more tightly than comma. For example FROM T1 CROSS JOIN T2 INNER JOIN T3 ON condition is not the same as FROM T1, T2 INNER JOIN T3 ON condition because the condition can reference T1 in the first case but not the second.

A LATERAL item can appear at top level in the FROM list, or within a JOIN tree. In the latter case it can also refer to any items that are on the left-hand side of a JOIN that it is on the right-hand side of.

This allows them to reference columns provided by preceding FROM items.

It is often particularly handy to LEFT JOIN to a LATERAL subquery, so that source rows will appear in the result even if the LATERAL subquery produces no rows for them.

Check both execution plans (using explain (analyze, verbose) and you'll see

Why not just use a join and group by? SELECT AA.ID, COUNT(B.ID) as no_tx, min(B.DATE) as fday_tx, max(B.DATE) as lday_tx, AA.start_date, AA.end_date FROM (SELECT ID, min(DATE) as start_date, max(DATE) as end_date FROM MAIN_TABLE WHERE CODE = 'drugA' GROUP BY ID ) AA LEFT JOIN MAIN_TABLE b ON b.CODE = 'drugB' AND b.DATE > AA.start_date AND b.DATE < AA.end_date GROUP BY AA.ID, AA.start_date, AA.end_date;

window functions: SELECT ID, SUM(CASE WHEN code = 'drugB' THEN 1 ELSE 0 END) as no_tx, MIN(CASE WHEN code = 'drugB' THEN DATE END) as fday_tx, MIN(CASE WHEN code = 'drugB' THEN DATE END) as lday_tx, start_date, end_date FROM (SELECT t.*, MIN(CASE WHEN code = 'drugA' THEN date END) as start_date, MAX(CASE WHEN code = 'drugB' THEN date END) as end_date FROM MAIN_TABLE t ) t WHERE code in ('drugA', 'drugB') AND date between start_date and end_date GROUP BY t.id;

The query to the right of the Lateral would be evaluated for every row of the left table.

"People should not be afraid of their governments. Governments should be afraid of their people."

Crush up a clove and let it sit at room temperature for 15 minutes. This allows a compound known as allicin to develop - a potent anti-bacterial agent which gives garlic most of its health benefits.

A fever makes the body less favorable to viruses and bacteria for replicating, which is temperature sensitive. Our grandparents knew this, but somewhere along the line mom’s began to believe a fever was dangerous for their child and would immediately try to lower it.

When you lower your child’s temperature with medications such as ibuprofen and acetaminophen, you are hindering your child’s ability to fight the infection. A better strategy to quickly fight the infection is to raise their temperature. Or at least leave the fever be so it can do its job.

this seems a very harsh decision to remove config and page level ssr now we’ll need to add a hook for just disabling ssr

I may be talking out of place here. As all core members have agreed on this. Apologise for that.

I think there should be an easier way to declare that pages/components should not be rendered on the server. Not all client-side-only code is bad!

Having both ssr: false in handle and export const ssr = false in pages, but with those subtly different semantics, would have compounded that confusion.

It wouldn't be good design to preserve the option on the offchance that it would still be relevant if Svelte gained an as-yet hypothetical feature.

that would only be a side effect of its main purpose

main purpose, get rid of annoying errors caused by side effect imports

In order to reflect this in the types I added an Either type to the helpers, because with Union Types only the values that the types have in common are directly accessible. So it would have been necessary to first check the returned type before accessing returned properties.

It should be | { fallthrough: true } rather than | { fallthrough: boolean } I think (there's no reason you'd have false)

The combined stuff is available to components using the page store as $page.stuff, providing a mechanism for pages to pass data 'upward' to layouts.

It's always a good idea to avoid things like 'both', since it's not future-proof — if we decided we wanted to support method overrides via headers, for example (which is sometimes used to get around firewalls that disallow non-GET/POST requests), then 'both' would need to become 'all', which would be a breaking change.

I agree about documenting everything. But for me docs are a last resort (the actual text, anything beyond skimming through code examples) when things already went wrong and I need to figure out why. But we can do much better. During dev when we see _method and methodOverride is disabled we can tell the developer that it needs to be enabled. Same if we see _method with something other than POST. Same for all other cases that are currently silently ignored. If the method is not in allowedMethods arguable it should even return a 400 in production. Or at the very least during dev it should tell you. We have the knowledge, let's not make the user run into unexpected behavior (e.g. silently ignoring _method for GET). Instead let's fail as loud as possible so they don't need to open their browser to actually read the docs or search though /issues. Let them stay in the zone and be like "oh, I need to set enabled: true, gotcha, thanks friendly error message".

In contrast to fetch the only valid methods for a <form> are GET and POST. Svelte allows you to override the <form> method to workaround this limitation if you need to. That way your application can transparently work when JavaScript fails or is disabled by using fetch and <form> interchangeably with the same endpoint.

It would be great if we could keep the existing behaviour for application/x-www-form-urlencoded, but we can't, because in their infinite wisdom the web's architects decided that a regular form submission should have that content type, but a fetch with the exact same data (i.e. body: new FormData(event.target)) will have a multipart/form-data content type. In order for endpoints to behave the same way with JS-triggered form submissions as JS-less ones, we need to have consistent behaviour.

There is something nice about aligning with the platform. But it risks being a straitjacket, and I think we can provide better ergonomics when it comes to streaming.