Dylanlacey

Yeah, their imperviousness to either progress or consequences is kind of incredible. An entire nation of collectivist, rule-following tendencies with a scummy layer of cartoonishly evil folks at the top, who for some reason seem immune from having to be decent people.

Delicious, but dealing psychic damage.

What I want to know is, what's happening to all the Australian rice they do import? Are the statistics lumping all varieties together, are we only selling them Basmati?

The agricultural minister went on TV and ate rice from one and two years ago from the stockpile and reported they were all delicious. People were _maaaaaaaaad_.

Yes, it is, and no, it's very much to the Japanese taste.

There's no absence of non-rice main meals in Japan; Wafu pasta is an entire category of Japanese pasta dishes whose name literally means Japanese Style Pasta. Udon, Ramen and Soba abound, and Kansai in particular has a large number of Konamon, flour-based meals and snacks (resulting from Allied food aid after the bombings).

In some ways, the reaction to suggestions of swapping out rice are like that redneck uncle of yours who is mad his Cardiologist told him to cut down on red meat because "what else am I supposed to eat?!" even though his wife does all the cooking and they already have pork/chicken/fish 3 nights out of 7. It's an identity thing; in some ways to eat rice is to _be_ Japanese.

Yeah, I've seen a fair amount of "but what will we eat?!" Netsuke-clutching and like... Y'all already have a trend towards bread for breakfast and you love your wafu pasta. Do that a couple of times a week.

But it's Japan, so I imagine there's plenty of Showa who think all change is to be valiently fought and that not eating rice prevents you from being "proper" Japanese.

I'm not sure tarrifs have a huge impact; Japan is Australia's largest buyer of rice, importing $63.8MUSD worth in 2023 per the OEC: https://oec.world/en/profile/bilateral-product/rice/reporter.... That's a lot of rice to buy, if it's more expensive and less desirable then domestic rice.

This^^ It's one of the gayest places on earth, of _course_ it's going to be more accepting.

It's interesting to me that no-one is talking about steel frames, which are becoming something of a standard in Australia, mainly because they share some of the advantages of both constructions styles.

A Steel framed, clad house can be constructed relatively quickly, but is also durable. Alterations aren't as easy as with wood, but are significantly easier then concrete.

With modern insulations and soundproofing, you can have a lot of the benefits of concrete or stone. Plus, there's less thermal mass in the structure, which is a big advantage when building in Australia; Your primary challenge is keeping the inside cool in Summer.

The cool part was that all of the extra JS Protractor used (sometimes for native WebDriver tasks) made things _less_ reliable.

Just curious, why do you prefer a first-party testing integration; Is it to save on harness maintenance or do you not like any of the stand-alone testing libraries, or something else? I guess I don't quite follow what you mean by "re-invent the wheel".

^^ All of this. I work for Sauce Labs; We've been pretty focused around Selenium but we're building out support for Puppeteer, Playwrite, Cypress et al.

The newer automation tools benefit from being newer; They can take advantage of hardened, well designed interfaces (like the Dev Tool protocol). Selenium's been around for a bit longer, and was built when browsers didn't make it easy to control them. That's influenced the semantics of Selenium quite a lot, as well as explaining the extra moving parts (Drivers exist to map the Selenium Wire Protocol (or W3C protocol) to whatever they're driving because Selenium wasn't built with a specific browser in mind).

I feel like, at this point in time, the real difference is how much abstraction you want from the browser. Selenium is a set of knives, Puppeteer is a Die Cutter. You'll put in more work with Selenium, but maybe you need something do happen a REALLY specific way. Or, you might just need shapes cut, and Puppeteer will be more reliable and faster.

The mad thing is, I would happily pay for the real estate sites to provide me with this kind of data because buying a house is so expensive and such a pain...

But it would STILL suck, because the input is so dodgy.

I work at Sauce Labs (inc. TestObject and Screener.io) and the Record-and-Playback tests are the ones that tend to be the most...

Not great. They're prone to timing problems and fragile selectors. They work well for rapidly recorded, rapidly changing sites (where you can throw them away) or very stable sites (where the DOM is basically fixed), but they rapidly become a hassle in the middle.

But they sure are easy. I'd suggest recording as a first pass, then going back and refactoring them to be a bit more stable; Change XPATH or structural CSS selectors to use classes and IDs, add waits and assert for page loads, etc.

That you were asked this question makes me a little sad.

Beside risks like Twitch (or worse, all of Amazon) blocking your traffic wholesale, letting someone use your product to abuse another is just a crappy thing to do; Especially if you let it because "well we're making money".

Storybook lets you permutate the inputs you can give a component, letting you verify the results are correct in a variety of ways.

I work for Sauce Labs, so I'm most familiar with combining Storybook with Screener (https://screener.io/v2/docs). Our integration lets you provide a set of interactions to take to change a component state, then does sophisticated layout, content, and structure comparisons.

The official docs for testing with Storybook have a range of other ways you can use it to test your components: https://storybook.js.org/docs/react/workflows/testing-with-s...

Aww, bless. Another article conflating technology with a negative outcome by ignoring the human factor, e.g. that safe sex is the responsibility of the humans not the app.

Media is so cute.

Travis CI is as free for Open Source as Github is; Notably, it also makes some of the other tools even sweeter (Like Code Climate, Sauce Labs, Github itself).

It's a little bit ironic that we can't alter the blog post about open source directly through comments, and instead have been asked to use Hacker News.

I, personally, don't want global legislation. I want either companies to not act like total dicks (Pricing in Ethiopia should be lower, pricing in Australia shouldn't be twice as much) OR for the AUS and US governments to make a joint agreement to, at the least, issue a large, nasty "Please Explain" from a body of authority.

But I am also coming from a background where the governmental consumer watchdog is very powerful, so that colours my opinions on what can/should usefully be done.

So there are often strategies put in place to ensure that an Australian customer can't purchase at the US price, on the basis that... well... fuck you we want your money that's why.

I would agree with your point if digital content producers didn't use geocoding to prevent me from accessing their US store o block non-US credit cards. The problem is not that this price is arbitrary, but that it's not. It's a deliberate, nasty piece of geographical discrimination.

We already had a monoculture; Opera not using Webkit wasn't preventing this because as you can see in the comments in this page, most non-Opera users considered its existence silly and never catered for it.

I love Opera. It's been my main browser since I started using the 'net (1996). But developers have always ignored it, always considered it not worth developing for because "there's no users". They didn't hold out against the monoculture, they just did their own thing for a while until they got tired of it.

And I think they are tired. They're talking about finally impacting the future of the web and being able to make widespread contributions. I think as a company they just love the Internet and want to be able to make it as awesome as possible for as many people as possible, and Presto wasn't allowing them to do that.

As an aside, feature copying was one of the greatest sources of irritation my friends had when Opera was still this really weird, unique thing that I used and they didn't. It was quite regular to have them excitedly tell me to switch to Firefox because "Dude, there's tabbed browsing, it's SO great!" Uh, thanks, I've... I've had that for years. But I'm glad you're discovering it too!

I'm not perfectly happy, there's not not much impact being unhappy is likely to have. Once a company makes a huge announcement like this, displeasure from the customer base is unlikely to cause them to change their minds until either they discover the change was a HUGE mistake and upsets lots of their customers and they lose significant market share OR they're forced to change because they go bankrupt.