Ahh, that's the worst. Hopefully you realized your mistake sooner rather than later.
539 karma · joined July 26, 2018
https://pixelalchemy.dev
A common sign of a bad API (including this one) is when it presents data in an overly human-centric way rather than something more computer-friendly.
For a human it's really easy to see "Regents Park" and "Regent's Park" are very very likely referring to the same station, but a computer can't know that unless a human goes out of their way to tell it that.
You could argue the TfL API is perfectly fine for its intended use-case of updating the arrival screens (which are meant for humans), but it's generally better to design APIs to grow for future use-cases you haven't thought of yet. Changing an API tends to be hard once it's being used in the real world.
For example: The older TfL stations have LED matrix displays for displaying information, which are very limited in how much text they can display at once. The newer stations have big TV screens instead, which can show a lot of information. It wouldn't surprise me if this is the underlying reason behind some of the inconsistencies, especially ones like "Kings Cross" vs "King's Cross St. Pancras". I'd bet the longer names with punctuation correspond to arrival displays in the newer stations.
Historically the only choice was permissive by default, so this is unfortunately the setting used by older organizations and repos.
When a new repo is created, the default is inherited from the parent organization, so this insecure default tends to stick around if nobody bothers to change it. (There is no user-wide setting, so new repos owned by a user will use the restricted default. I believe newly created orgs use the better default.)
[0]: https://docs.github.com/en/actions/security-for-github-actio...
It won't be plug and play since you'd have to pull out the shaders and make them work in your app, but the implementation supports quite a few material variants. The PBR shader implementation starts in source/Renderer/shaders/pbr.frag
It is possible to do that in the general sense though.
It's basically an ongoing large-scale research project working to quantify the way people experience city spaces from a neuroscience perspective (or at least that's my understanding -- I work with some of the people who are working on it.) Maybe the work they're doing could be relevant to what you all are doing?
Updating both Git and Git Extensions has seemingly fixed it for me, but the issues I was having were sporadic so maybe I've just been lucky
That might be all you need to fix the F# REPL too.
I haven’t had a chance to look into it further so I don’t know if it’s any good, but it might be worth looking into. (I’m also curious if anyone here has experience with it)
In particular it lists some other studios not mentioned in this one:
The US based studios and groups impacted by a reduction in workforce are:
* Insomniac Games, Naughty Dog, as well as our Technology, Creative, and Support teams
In UK and European based studios, it is proposed:
* That PlayStation Studios’ London Studio will close in its entirety;
* That there will be reductions in Guerrilla and Firesprite(However I agree with the other comment about HN not being representative of typical users.)
Link rot is always disappointing, but I actually expected it to be far worse for links from 17 years ago.
* Conceptual docs: https://github.com/dotnet/docs
* BCL: https://github.com/dotnet/dotnet-api-docs
* ASP.NET Core: https://github.com/dotnet/AspNetCore.Docs
* WinForms/WPF: https://github.com/dotnet/docs-desktop
The C# language specification is unfortunately a bit fuzzier, but the conceptual docs above include what most people want: https://github.com/dotnet/csharplang/discussions/4855
The updated unified C# language specification is CC, but it's still catching up to modern C#: https://github.com/dotnet/csharpstandard
I can't comfortably use JetBrains products because they're really bad about letting you actually disable these things. VSCode extensions also love to add their own little settings that don't respect the higher level ones. Visual Studio previews somewhat frequently ship new "helpers" like this without a way to disable them (to their credit though, they do quickly add one once you point it out.)
I too wish more apps offered a top-level "disable everything unless I explicitly enable it" setting. Figuring out where the individual settings are buried only exasperates the frustration.
According to them/Wikipedia, the layout's name is simply "circular layout". https://en.wikipedia.org/wiki/Circular_layout
As someone who takes care of their stuff, it's pretty annoying to get my books pre-worn.
This made me double-check the date of the article (it's from 2023.)
The author's laptop appears to have launched in 2020. I'm astounded any manufacturer would think this is even remotely acceptable this day and age, much less on such a high-end device. (Going off the current generation, these laptops start around $3k.)
Is this actually that common or did the author just get unlucky?
If it weren't for a friend giving me his old iPhone XS as thanks for a favor, I'd probably still be using my old iPhone 6s--and I would not have worried about it from a security perspective purely because (as the article notes) Apple is still releasing security fixes for iOS 15. I'd feel differently if Apple had publicly stated that all iOS 15 security fixes from now on will be on a minimum effort basis only.
For your second goal, if you're referring to implementing your own ray tracer I highly recommend the Ray Tracing in One Weekend series: https://raytracing.github.io/