acherion

Weird, I scrolled down to see what cameras it supports, and there was a link labelled "Supported Cameras" that goes to https://rawspeed.org/CameraSupport.html but that's a squatted domain now. Is there a list somewhere? It doesn't instill much confidence in me if I can't even see what camera RAW formats are supported.

Actually I do have a special needs kid (my daughter is deaf). I do keep my door open during work hours.

> There's less distraction and better divide between work and private time. When I leave the office, I'm done for the day.

I am glad I have the luxury of having a separate room as my home office. When I’m done for the day, I leave that room and close the door, and don’t go back in unless it’s the next day or an emergency.

If you're interested in the Trabant, the Youtube channel Aging Wheels has a couple of playlists where Robert has rebuilt the engine and gearbox of his [1] and just general videos [2] about his Trabant.

[1] - https://www.youtube.com/playlist?list=PLzV2uljPvyAeEgAEgwYNf...

[2] - https://www.youtube.com/playlist?list=PLzV2uljPvyAe1K8ArgPHG...

> the most common mobile browser resolution is 800x360

Really? You're saying most people are using their mobile phone in landscape mode?

I'm very excited to see this release! I've been working on personal projects with 1.x of PayloadCMS, and coming from the Wordpress / PHP / Laravel world it's been a breath of fresh air developing in TS, but I did miss some of the Laravel-esque aspects like db migration.

Adding support for Postgres (and I assume other DB engines in future) is a monumental task and I commend you all for doing such a good job – granted I haven't used it yet but I do look forward to!

And I am loving the support for Lexical, SlateJS did not jive well with me, so the ability to have options is great.

Having a look at the Richard Stallman entry in Wikipedia[0] it menions this quote you're referring to, which links to this Engadget article[1] that links to rms's blog with that specific entry[2]

[0] - https://en.wikipedia.org/wiki/Richard_Stallman

[1] - https://www.engadget.com/2019-09-17-rms-fsf-mit-epstein.html

[2] - https://stallman.org/archives/2019-jul-oct.html#14_September...

I had this occur with my 2004 PowerBook back in the day, it was pretty bad. At the time I had found a company that made adhesive transparent stickers that you could place on either side of the trackpad that would protect the aluminium from being eaten away by the sweat on your palms.

I bought this when I upgraded from my PB to my Core 2 Duo MBP in 2007, fearing that this newer machine would suffer the same fate as my PowerBook, but all is well and that machine didn't experience pitting.

Having said that, the pictures in the link are pretty bad, I've never seen pitting that bad before, that looks horrendous!

It sounds like to me that the complaint is why Poland hasn’t switched to green power already. A comment like that demonstrates a lack of understanding about the levels of effort to make such a change, as if the change to green power is as instantaneous and painless as flicking a switch (pun half intended).

I guess families with young kids that would have to leave the kid in the window aisle, distressed and upset while the only people they know are leaving them in a vessel with people they don't know, are just not "enlightened" enough.

I implore you to consider the group issue in more detail, and perhaps with a touch of human empathy this time.

First entry on their History page says it was: http://wiki.aminet.net/index.php/The_history_of_Aminet

A lot of shareware was also distributed on coverdisks for computer magazines. Not sure if this was a thing in North America, but in Europe and Australia, coverdisks were very popular.

Is this app only available in the US app store or something? I tried on my iOS device here in Australia, and a whole heap of other mapping apps are appearing in search results instead, when the query string is "magic earth". iOS App Store is even autocompleting to "magic earth navigation & apps" but no Magic Earth app appears in the results.

If the videos don't load for you, try without an ad blocker (or put this site as an exception). I use Ghostery and the videos wouldn't load unless I trusted the site. I tried trusting just some of the components in Ghostery but they still wouldn't load unless I trusted the entire site (not just all of the trackers it listed).

Doing something interesting comes with risk. That billion dollars is likely cash from investors who want a return. They won't be happy if the interesting thing you want to do isn't going to return a profit, hence they stick with what they know best and is least risky.

>The marbles that were bought

From whom? Whoever Elgin paid money to certainly didn’t own the marbles, and the firman that he quoted doesn’t exist. He helped himself to set up his own personal museum.

>from being ground up to be made into cement

Only the marble that was on the ground was ground up into lime. Elgin pulled friezes off the Parthenon, that’s a big difference.

The Acropolis Museum has spaces reserved for the return of the marbles to their ancestral home. A museum that’s climate controlled and employs people who care about these artifacts a lot more than the British Museum [1]

It seems to me that the people running the British Museum want to hold onto the Marbles lest other governments demand their antiquities back, if the Marbles ever make it back home.

[1] https://www.ekathimerini.com/culture/1166224/possible-water-...

They're British. We're talking here of the same people who used copper tools and wire brushes on the Parthenon Marbles that they stole, so that it could be more "pure white".

Good thing my browser settings are to show scrollbars all the time!

> Instead of capping prices, you could simply require any fees to be paid by the cardholder.

This already happens in Australia. The price is the price, until you go to pay and if the shopkeeper sees you pull out a credit card, would adjust the total to include a 1.5% surcharge (Visa or Mastercard, and you'll likely be turned away if you pull out a different card like Amex).

The problem with this is that especially since Covid, a massive percentage of in person sales are done via contactless credit card payment, sometimes even with the screen of the terminal not even in view of the cardholder. Some sellers have caught on to this and are charging _much_ more than the 1.5% -- three sushi handrolls at the store around the corner of my workplace would cost about 9 AUD to buy (already includes GST), but the shopkeeper then added a whole 1 AUD on top for surcharge. I protested and have not shopped there since, but there's still plenty of customers at that store.

More and more stores are adding 50c or 1 AUD on top to cover surcharge for items well under 10 AUD, I'm guessing because calculating 1.5% is not trivial for a lot of people, and are ripping off their customers. Calculating 2.08% in your head to make sure the shopkeeper is not pulling a sly one on you unfortunately is not something a lot of people are going to do.

The article clearly states that the yellow dots are printed by _colour_ laser printers.

So GoDaddy still does this, huh? I was stung in the very same way over 15 years ago, looks like their business practices haven't changed much since.

Right, but this is a discussion about their documentation, not whether Feature X in a version of Laravel is still around in the latest version. I'm not attacking the framework, as I said I love using Laravel. I just have criticism about their documentation.

I struggled with sorting out Contracts vs Facades vs Traits. I graduated from university 20 years ago with a software engineering degree, where it was drummed into me that simpler often is better, and much more robust. Reading the Laravel docs however, leaves more questions than I started off with.

eg. https://laravel.com/docs/5.8/contracts – talks a lot about how Contracts are powerful additions (like all the other features of Laravel, the docs are good at telling you they're powerful) and the examples show just some barebones code that doesn't really do much without a lot more work. The examples in the documentation seem to be more on the side of being some code snippets that don't convey much context.

Additionally, there's lots of "congratulatory" text in the documentation ("Laravel has a powerful feature called <x>", "in Laravel adding <feature y> is actually really simple", "some developers enjoy using <feature z>". You simply don't see this in PHP.net's docs, it just tells you what the function / feature is, gives you examples that work straight out of the box, lets you know of any pitfalls or differences in PHP versions to watch out for, and there's a whole list of comments contributed by other PHP devs spanning years, that are up/downvoted.

Another example of powerful documentation was that I learnt what MPTT is, and how to implement it effectively, purely from CakePHP docs back in the day (I'm talking v2 here). I can't see how anything as remotely useful would be able to be taught from Laravel docs alone; for someone who doesn't have a computer science degree, there would be a LOT of tabs open, full of rabbit holes that need to be explored. This is not effective documentation in my eyes.

The difference between these sets of documentation is like night and day to me. The Laravel docs needs to stop patting itself on the back, and be more like other software projects' documentation.

Don't get me wrong, I love working with Laravel, it is powerful. My issue is with the documentation, which leaves a lot to be desired.

> Laravel is [...] reasonably well documented

Hard disagree. Sorry, I don't have a computer science degree, why does their documentation make that assumption. I find their docs very hard to grok.

PHP.net docs are no-frills no-fuss, straight to the point. Other frameworks are documented very well too, CakePHP comes to mind (at least, when I was using it last in v2 and v3).

I can't say I've read the absolute latest version of their v10 docs, but when I was neck deep in 5.8 I found I had to switch to older versions of the documentation to read up on some of the most basic of Laravel features. eg. What's the syntax of using Form in Blade templates? I had to go back to v4.x docs to read up on it, Blade templating hardly got a mention in v5.x documentation, despite it being critical component in a Laravel application.

If there was a bug in a project and I had management breathing a fire down at me because it's breaking the site / losing sales / stopping monthly reports from going out, I shouldn't need to decode computer science terms, or look through previous versions of documentation to find the solution.

This is why, in my opinion, Laravel documentation sucks hard.

Many years ago I got mylastname.com for a normal price (like $20 a year or whatever) and then forgot about it. It helps that I have a very unique surname.

A few years afterwards, I woke up one morning with the bright idea that I should probably secure mylastname.com in case some jerk off domain name squatter grabs it. I do a whois from the command line (I don't trust the online domain name search sites anymore) and saw that it was already taken! What the hell! My last name is so unique, how did anyone know, let alone a domain name squatter, to snap this domain name from under my nose!

I go to try and find more info about the domain outside of what was in the whois info (eg. who should I contact to try and negotiate a price for mylastname.com) but the domain didn't go anywhere when typed into my browser. Bummed out, I go into my usual domain name registrar dashboard to try and perhaps get the .net version or something, and there I saw in my list of currently owned domain names, the very mylastname.com domain I was looking at buying.

The squatter was me all along! </callWasComingFromInsideTheHouse>

A registrar I use for my local domains (I'm in Australia, and use a local registrar for .au domains) has my CC details on file including the expiry date. They send me an email out a couple of months before the expiry date reminding me to update my CC details, which is nice.

The machine depicted in the clip is an Apple IIe, which first came out in 1983. But this might not be a 1983 model, because the monitor depicted with the machine is the ColorMonitor IIe, which came out in 1985. Because it's a computer used on a set for a TV show, it's possibly a loan machine, perhaps from Apple themselves, so it was likely supplied as a new computer + new monitor combination. So I'd hazard a guess and say this setup is from 1985 or later.

If we take my previous assumption further, the Platinum IIe was released in 1987, which came with a numerical keypad built in, and looks distinctly different from the IIe. Even though this Youtube clip is 240p, you can distinctly see that there is no "divide" in the keyboard, so this is definitely not a Platinum IIe.

I would say this machine was manufactured between 1985 and 1987.

I had read some years ago that putting this "fee" on sending email wouldn't really deter the spammers, when they find one sucker (and they do find them, and there's usually more than one) they can extract so much money out of them that it would still be worthwhile to spend the pennies sending those emails.

The indicator should be on the outside, so you can change gear (in a manual transmission car) and indicate at the same time. It's just common sense.

I am used to the indicators on the left though when driving my BMW, so I experience the classic "wipers instead of indicators" dance many times when I drive my wife's car. As most cars nowadays are automatics, I guess this reasoning is falling out of relevance more and more.

I also want to note that not all Australian built cars had wipers on the left and indicators on the right – many GM Holden models like the Kingswood and early Commodore models from the 1980s had them both on the one stalk – that stalk being on the right of course.

And it's not always reversed! Australian-made and Japanese-made cars tend to have indicator on the right stalk, and wipers on the left. European cars tend to have indicators on the left stalk, and wipers on the right. But not always!

Case in point: my wife and I live in Australia (have done so all our lives), and my wife had a 2008 Ford Focus, made in South Africa (a RHD country). Indicator stalk was on the left, wiper on the right (aka "European" style). She then upgraded to a 2020 Ford Focus, made in Germany (it's the wagon model), and the wiper is on the left, indicator on the right. Which confuses me, as I drive a BMW, which has indicators on the left and wipers on the right.