> Gitlab ships various ci runner executables for all platforms. I use their Windows ci runner and it works well, but I wonder how they test it without running windows.
It is prohibited at Gitlab according to this policy. On developer laptops. It is not necessarily prohibited in all contexts. The one-line title could've been slightly clearer, but I think it's a totally fair statement.
The prohibition on developer laptops is not just a trivial or nitpicky detail; while the security of a VM obviously still matters, as you can't simply assume that malicious software in the VM can't escape, I would assume that the policy effectively means it would also be prohibited to setup a Linux dom0 and just run Windows under that and use it as your developer workspace. The benefit of only using Windows for testing is that you presumably won't be reading emails, talking on team chat, taking video calls, opening documents, etc. inside of Windows, only doing the thing you actually need (testing.) From a security standpoint, this can be helpful. I think that Windows vs Linux security is a rabbit hole not worth debating; both are very flawed and have many challenges, nothing is a panacea. However, I would say that every OS you don't need to harden is a huge operational advantage no matter how you slice it. You effectively cut off an entire slice of the malware market, and easily the largest slice in case of Windows.
Sure thing. Further down in another comment I went into how the music is made, so I'll stick to the tech stack here.
The frontend is built with React, Chakra UI and Tailwind CSS. It also does all of the audio generation using a scheduling library called Tone.js.
Auth / Database are handled by Firebase, and payments are by Stripe. It's fully serverless; I use cloud functions for anything server side.
The samples themselves are stored in Google Cloud Storage, although I may need to look into a different method or making it more efficient, as today's traffic has absolutely smashed through the free downloads tier.
> Or in case of Europe in an international company a team decides to hire only people that speak german / russian / french even when the interaction with other teams is obviously just in english.
You're clearly conflating ethnicity with language.
1/ Just because people talk the same language doesn't mean they have the same ethnicity.
ex: French is spoken as a native language on every continent.
2/ Just because people have allegedly the same ethnicity, doesn't mean they share the same language or even culture.
ex: All black people living in Africa do not share the same culture, yet Americans reduce black people to a single ethnic group.
> Well the US definition of diverse is much more picky about what diverse means.
Yes, in US the definition of "diverse" is politically loaded, implying you subscribe to a specific partisan ideology. It's so loaded that you can't talk about diversity as "diversity of opinion", it has to be racial
I am not conflating anything. I have had a very similar experience in EU and Singapore and while the case of Singapore is ethnic preference in EU it's about the language even if the working language is english.
> I am not conflating anything. I have had a very similar experience in EU and Singapore and while the case of Singapore is ethnic preference in EU it's about the language even if the working language is english.
Are you complaining that people in Europe talk their native language instead of English and that a company located somewhere prefers hiring locally? Whether a company is international or not is irrelevant.
You are certainly implying that 2 distinct situations are equivalent and it's "a problem" for you. I don't see where the problem is, personally.
Now if you have witnessed specific instances of racism or racial discrimination at work or during the hiring process, then you should report it to HR or the proper local authorities.
You have an international company located in Europe where daily business is conducted using english. There are naturally diverse teams with people from different countries (as is the case in Europe) and then there's one team where a hungarian manager decides to hire only hungarians.
You dont find this to be problematic in any way?
The same applies to Singapore where the pool of candidates is large and diverse but a certain for example indian manager decides to hire only indians.
I actually find Chrome to be faster and generally appreciate the contributions that Google has made to try to keep the web competitive with the proprietary platforms, but I can't get past the auto-start video issue.
You know that Chrome tried to remove auto-start videos and advertisers just ended up writing their own battery sucking slow canvas based software decoders?
That Firefox is doing this is very much like yesterday's new Facebook URL
By default firefox only prevents content with audio from autoplaying, which I can't think of any way to circumvent and it's probably good enough for most people.
Yet all the summer music festivals are packed, sold out within minutes. It's just that the kids value live experience more than they value mp3 or Spotify.
Clearly no, because Vala has a bunch of issues with memory safety. Not because it's a bad language, but since it translates directly to GObject, there is a lot of problems around pointers, ownership, ... mainly because that language lacks maintainers and GTK/Gimp developers didn't like it because they are "C essentialists".
"C essentialist" is a line very hard to hold, because C via ISO is moved towards an horrible language like c++ (generic,__thread,etc). So, it is not C anymore, it is simple and lean C which should be the target of an essentialist line of conduct.
Whatever, a good new language would first and above all be easier to write a compiler for than simple C.
To access TLS-ized system variables (for instance errno if I really need to, I would use the sysv ABI __tls_get_addr() function).
But in the application domain, I would use pthread TLS.
No, pthread TLS is the slower one. Accessing system TLS can be done fast since lib knows the details of the implementation and, worst case, it can use inline assembly.
Also, pthread TLS adds a pointer dereference to each access.
The compiler does not know the inner layout of how the system TLS variables are stored (could be musl way, bionic way, glibc way, etc). It only knows that for system TLS variables it has to go thru __tls_get_addr(), stated by the sysv ABI. Indeed, you are not forced to use pthread TLS to cache the value, you can use your own thread allocated memory, or keep it around on the stack/regs. On x86_64, once you have resolved the address with __tls_get_addr() you can use the same address value for all threads, then use common to all thread storage.
Riccitiello: Ferrari and some of the other high-end car manufacturers still use clay and carving knives. It’s a very small portion of the gaming industry that works that way, and some of these people are my favourite people in the world to fight with – they’re the most beautiful and pure, brilliant people. They’re also some of the biggest fucking idiots.
To be fair, the full comment is even more belittling than the sound bite. It’s almost dripping with contempt for those who have a different set of values than him.
It's ironic you say that because as someone who arguably fits in the category he's talking about (see: my bleeding heart comments about Unity's for-profit asset store from yesterday) it feels somewhere between belittling and insulting for people to act like grown adults would really miss what his point was.
There seems to be this "rainman-esque" infantilization of people who put craft before profit that I truly deeply hate. He spoke like he was having a frank, open, conversation. That relies on everyone involved being somewhat mature and not jumping to the worst possible interpretation of everything.
But I don't know, maybe people are right to treat "the creatives" with the kiddie gloves based on the reaction I've seen.
There is no such thing as a "REST standard" and that's why we've been having all these pointless arguments for the last 15 years. If Fielding really wanted web developers to use REST he would have wrote a normative spec about REST.
Seems to me that REST was never about developers writing web API. The whole "smart client" capable of API discovery through "hyperlinks" is... a browser with a user clicking on those links. Except that API aren't consumed by browsers but other apps that are neither as smart nor complex.
2 wrongs don't make a right. Uber operates like the mafia. I'm not going to take their defense just because they are a "just an app" or that the competition is as bad...
Uber became popular because it leveraged VC and cheap credit to subsidized rides, it's becoming much less popular as we speak since ride fares are going up fast and it now needs to actually make money.
same here. I miss Fireworks, a software that didn't try to nickel and dime those who wanted to do both vector and raster graphics with the same tool, and it worked very well for website prototyping. great addon community as well, thanks to JS integration.
Maybe with a Windows VM.