Bought a ferry ticket, it told me I am close enough to board. The usual popup for advancing time to leaving time didn't show up. Decided to speed up time and wait it manually it just kept going without getting in until 2am when out of hotel triggered game over.
One of the 2 terminals in Cherbourg France, the city you reach by traveling from Dublin to France, but not the one I arrived in. It only had routes to England.
Similar thing here. Was in a ferry from Ireland to France and got a penalty for not being in a hotel. How is 20 hour ferry not considered an overnight transport.
It's not that different from "real 3d" renderers. Especially in deferred rendering pipelines the rasterizer creates a bunch of buffers for depth map, normal map, color, etc but main shaders are running on those 2d buffers. That's the beauty of it parts operating with 3d triangles are kept simple simple and the expensive lighting shaders run once on flat 2d images with 0 overdraw. The shaders don't care whether normal map buffer came from 3d geometry which was rasterized just now, prerendered some time ago or the mix of 2. And even in forward rendering pipelines the fragment shader is operating on implicit 2d pixels created by vertex shaders and rasterizer from "real 3d" data.
The way I look at it if the input and math in the shader is working with 3d vectors its a 3d shader. Whether there is also a 3d rasterizer is a separate question.
Modern 3d games are exploiting it in many different ways. Prerendering a 3D model from multiple views might sound like cheating but use of imposters is a real technique used by proper 3d engines.
Unfortunately, the 2D imposter mode has pretty significant difficulties with arbitrarily rotated 3D. The GBDK imposter rotation demo needs a 256k cart just to handle 64 rotation frames in a circle for a single object. Expanding that out to fully 3D views and rotations gets quite prohibitive.
Haven't tried downloading RGDBS to compile this yet. However, suspect the final file is probably similar, and pushing the upper limits on GB cart sizes.
I disagree with Apple caring about legibility. You can have legibility in simplicity but apple isn't doing that.
Legibility requires contrast, the whole liquid glass transparent background thing kills contrast and thus legibility. Having random noise from the background windows kills legibility.
As for icons specifically - having white semitransparent (vertical gradient) shape on top of brighter color background makes it harder to perceive the shape which is currently only remaining distinguishing feature. Half of them are gray on gray. If you can't recognize the shape while squinting your eyes then it's not a good legible shape for icon.
The Messages/FaceTime is other comments mentioned is one of the best/worst examples of this. In theory shape of camera and speech bubble are unique, but in practice the real difference is very small. They are both similar size elongated blobs. Messages have tiny little triangle in bottom left corner, camera has two notches. Overall and in combination with color choice this makes it harder to recognize the shape. Phone also uses the same color but at least the general shape is significantly different.
It's not all completely bad. The rainbow button strip and darker background for Audio Midi setup in my opinion made it more distinct. The contact icon also improved contrast, but only because old one had very bad contrast.
There are plenty of others where contrast was made worse. For example Time machine, Font book, Clock, Finder.
Not exactly real world, but real code example demonstrating strict aliasing rule in action for C++. https://godbolt.org/z/WvMb34Kea Rust should have even more opportunities of this due to restrictions it has for writable references.
There are 2 main differences between versions with and without strict aliasing. Without strict aliasing compiler can't assume that the result accumulator doesn't change during the loop and it has to repeatedly read/write it each iteration. With strict aliasing it can just read it to register, do the looping and write the result back at the end once. Second effect is that with strict aliasing enabled compiler can vectorize the loop processing 4 floats at the same time, most likely the same uncertainty of counter prevents vecotorization without strict aliasing.
If you want something slightly simpler example you can disable vectorization by adding '-fno-tree-vectorize'. With it disabled there is still difference in handling of counter.
Using restrict pointers and multiple same type input arrays it would probably be possible to make something closer to real world example.
Windows11 making it hard to create a local account is a separate topic.
The fine print notes refer to to specific features. In this cases it's "4." for Copilot.
You don't need apple account if you are fine with not using half the features listed in the marketing page for apple hardware. If you looked at the bottom of page for any of apple computers you will see similar fine print. For example https://www.apple.com/macbook-air/ .
> 22 Requires that your iPhone and Mac are signed in with the same Apple Account using two-factor authentication, your iPhone and Mac are near each other and have Bluetooth and Wi-Fi turned on, and your Mac is not using AirPlay or Sidecar. Some iPhone features (e.g., camera and microphone) are not compatible with iPhone Mirroring.
> 23. SMS requires an iPhone or iPad with iOS 8.1 or later or iPadOS. iPhone calls require an iPhone with iOS 8 or later.
> To access and use all Apple Card features and products available only to Apple Card users, you must add Apple Card to Wallet on an iPhone or iPad that supports and has the latest version of iOS or iPadOS.
> iMovie, GarageBand, Pages, Numbers, and Keynote are available on the Mac App Store. Downloading apps requires an Apple Account and a device that is compatible with the OS version required for each app.
And seems like there are a few more things advertised as features of specific apple hardware which probably won't work without apple account but lacks fine print at the bottom for example iCloud.
> Windows11 making it hard to create a local account is a separate topic.
Hard is a generous take. They litterally removed their offline phone mode.
> You don't need apple account if you are fine with not using half the features listed in the marketing page for apple hardware.
Can you name the hardware features? Because Apple take the approach of opt-in in my experience. And don't get me wrong.. I'm adamantly pro choice.
Features are one thing. Getting installed without an account is another thing. Imagine now you buy a laptopwith windows, you can activate it until you connect to the internet.
Apple, buy a notebook. Install the os. Nice airgapped system to test with.
Added software is another story. You're conflating the two I feel.
> You don't need apple account if you are fine with not using half the features listed in the marketing page
I want an OS I paid for. Why should I connect to your CNC?
> buy a notebook. Install the os. Nice airgapped system to test with.
Whereas Microsoft provides testing images, so you don't need to kill the planet just to test if a link really looks blue.
Why are you trying so hard to apologise for one of the worst corporations in the world? They are all bad and they all want the same things from you (money and personal data); they just go about it in slightly different ways.
> They are all bad and they all want the same things from you.
I actually do agree with you on this, but my level of acceptance draws a line in the sand and where Microsoft has gone is past it. No, Apple is no Saint but these days there's no harm in pointing out the difference.
I would guess that it also helps with accidental restarts due to power loss while repositioning the keyboard on your desk. It doesn't take much force to pull out USB-C.
Has it actually reached properly functional state?
The showcase video didn't look very convincing and neither website nor the discord channel contained a lot more information. Although I didn't dig through discord history too carefully.
It's one thing to hook up 200 hall effect sensors to a MCU, and read few of them or send data over HID at 8000Hz. It's different thing to read all 200 at 8000Hz and figure out the position with reasonable resolution and accuracy.
Can it also detect the exact moment pen touches tablet or additional button clicks? Or does it require taping keyboard with other hand? Which is probably fine for OSU, but less so for drawing.
Regarding the last point, pompyboard is very much a tablet or pointing device meant only for enthusiast osu! players from what I understand. No artist in the world needs a 8KHz polling rate tablet let alone 1KHz. Tablets from other brands are much better suited for drawing.
While the basic idea of a rectangle you put a pen on is the same for artists and osu! players, the more detailed requirements are basically opposites
Basically:
- Pen click is useless for osu! or can just be digital, while artists would want analog pressure
- Buttons on a pen are actively detrimental for osu! but very useful for artists
- Smoothing on a tablet is more detrimental for osu! the more of it there is but absolutely necessary for artists
- High polling rate is useless for artists (they would have input delay due to the smoothing they need either way) but very useful for osu!
- Big tablets are useless for osu! players as they typically only use a 5-15cm area while they are very useful for artists
I think the entire point of something like pompyboard is to make a tablet just for osu!, which doesn’t exist right now. Meanwhile for artists there is already a whole industry of tablets available for them
Except your giant comment doesn't actually explain why it used uint64. Only place mentioning uint64 is integer promotion which only happens because you used 64bit integer, thus no explanation of why.
Was it done because shifting by amount equal or greater to integer width is undefined behavior? That would still not require storing result in 64bit mask, just shifting (~0ULL) would be enough. That would be a lot more valuable to explain than how bitwise AND works.
The first one also seems slightly sketchy but without knowing rest of details it's hard to be sure. IPV6 address is 128bits, that's 2 registers worth integers. Calculating base address would take 2 bitwise instruction. Cost of copying them in most cases would be negligible compared to doing the lookup in whatever containers you are searching resulting address. If you are storing it as dynamically allocated byte arrays (which would make copying non trivial) and processing it in such a hot loop where it matters, then seems like you have much bigger problems.
For my taste it would be sufficient to say "Iterate in reverse order from most specific address to least specific. That way address can be a calculated in place by incrementally clearing lowest bits." Having 2 paragraphs of text which repeat the same idea in different words is more distracting than it helps.
Sorry, I didn't explain uint64 was used. I wrote this many years ago so my memory was foggy, but I went through a few iterations using uint32 only to use branches for the masks. This was the only branchless way I could come up with at the time after a few attempts. I think the example was more to demonstrate that the algorithm was correct and I wasn't going to unit test it at that scope.
As for the 128-bit addresses, we used boost ip::address_v6 to_bytes() as it appears there was no masking option.
For my taste it would be sufficient to say "Iterate in reverse order from most specific address to least specific. That way address can be a calculated in place by incrementally clearing lowest bits." Having 2 paragraphs of text which repeat the same idea in different words is more distracting than it helps.
Ah apologies, too late now, should've mentioned it in the PR. But I expected it would ruffle some feathers, I don't care for conventions or other people's quibbles. As long as it improves understanding for the reader, regardless of how "redundant", then mission accomplished.
If you had read the link you posted you would know those are various historic proposals for language reforms not something that's widely used. Same way there have been various proposals for English spelling reforms. That's not the normal way for writing or reading Russian. Russian uses Cyrilic alphabet which if anything is closer to Greek alphabet than Latin. There are other slavic langauges which actually use Latin based scripts. If you don't read Russian it might look like some of the letters look similar but that's only less than half of alphabet and from those half have completely different meaning than Latin lookalikes.
Yes there are various schemes for transliterating Russian into latin script, which people occasionally use for various reasons like typing on a computer or phone which hasn't been fully configured for use with Russian language, in contexts where unicode isn't supported or to make street signs legible for tourists. That's different from the "Russian Latin alphabet". In most cases where proper Cyrillic is problematic dedicated "Russian Latin alphabet" that's based on Latin with extra diacritic marks would also be problematic.
Similar thing could be said about other languages like Japanese or Chinese, but I don't think anyone would describe them as "languages that use the Latin alphabet".
As for typing on keyboard the main Russian layout is nothing like qwerty. Computer keyboards sold in relevant regions often have dual labels. I personally never learned touch typing in Cyrillic and use the phonetic layout in the rare cases I need to do so since for me it was a second foreign language.
Which exact approach Click chose - who knows. Will it be possible to choose your preferred Russian layout like on a desktop computer? Likely not. If they supported that I would have expect them to also add layouts for more languages. Although maybe they didn't want to promise anything for languages for which they don't have OS UI translations.
Fortunately, I then assumed that I knew nothing and asked anyways. I'm glad I did — this thread is now much more interesting than the one-word comment conveyed to me at first.
reply