ko27

10 ms·

61.
by ko27 3y ago
You are right, I don't know why you are downvoted. META can't charge depending on your tracking consent, they'll have to do it for everybody in the EU.
62.
by ko27 3y ago
> Big if, not everyone is using .NET latest on VS, with latest version of every library using async/await. The analyzers are part of the build, they work everywhere (command line, VS code). Either way, I am glad we finally agree tha
63.
by ko27 3y ago
> Ah the usual argument that good programmers never make mistakes. Not my conclusion at all. I am saying that tooling and base libraries have matured enough to prevent those issues from happening. > because basically now it is too lat
64.
by ko27 3y ago
Yes it does. Those best practices are very easy to follow and are enforced by analyzers. I have never encountered those issues on a recent big project I worked on, although they were common in the past when async was new. Also the green thr
65.
C# Green Threads Technical Report(github.com)
3 points by ko27 3y ago|0 comments
66.
EU delegation visiting Cupertino to negotiate with Apple on the USB-C(old.reddit.com)
4 points by ko27 3y ago|0 comments
67.
EU member states still cannot agree about end-to-end encryption(cyberlaw.stanford.edu)
2 points by ko27 3y ago|0 comments
68.
Did the React team forget the React Forget compiler?(old.reddit.com)
2 points by ko27 3y ago|0 comments
69.
by ko27 3y ago
> demonstrates that such measures are necessary and justified and that there are no less-restrictive means to safeguard the integrity of the hardware or operating system Example how this would play out: 1. Apple bans every 3rd party app
70.
by ko27 3y ago
No. 3 (only Apple-approved 3rd-party App Stores) is definitely not compliant. No. 4 (legally obligated to give Apple cut) is flat out wrong. While it might be true that Apple's 30% cut is not ruled illegal, it's a far cry away fro
71.
by ko27 3y ago
15 Pro has the same brightness specs as 14 Pro.
72.
by ko27 3y ago
Your conclusion is wrong. There is no difference in battery life if you compare to 14 Pro on their site.
73.
by ko27 3y ago
The reason is pretty simple. It's because those 1st party frameworks are awesome. There is very little reason to build something else when you can contribute to them instead. ASP.NET is crushing other web frameworks in performance on t
74.
by ko27 3y ago
> five times slower than what, where Slower than the time we measure here on Earth, or outside Earth/solar system/galaxy. They are very minor time dilation differences between those cases. > In particularly, how can you say
75.
by ko27 3y ago
Slower relative to the low density universe average today, which is pretty close to the time we experience on Earth.
76.
by ko27 3y ago
Note that it's impossible to actually see quantum entanglement or the wave function. This demonstrates an interesting way to visualize it.
77.
by ko27 3y ago
Where?
78.
by ko27 3y ago
Okay, it's good that we agree then on my original premise, the vast majority of websites (by quantity and popularity) on the Internet today are using UTF-8 encoding, and Latin-1 is being phased out. Btw I appreciate your edited respons
79.
by ko27 3y ago
Not including charset="utf-8" doesn't mean that the website is not UTF-8. Do you have a source on a significant percentage of website being Latin-1 while omitting charset encoding? I don't believe that's the case. &
80.
by ko27 3y ago
You should read it again > Newly defined header fields SHOULD limit their field values to US-ASCII octets ASCII octets! That means you SHOULD NOT send Latin1 encoded headers. The opposite of what pzmarzly was saying. I don't disagre
81.
by ko27 3y ago
> should be sent in Latin1 Do you have a source on that "should" part. Because the spec disagrees https://www.rfc-editor.org/rfc/rfc7230#section-3.2.4 : > Historically, HTTP has allowed field content wit
82.
by ko27 3y ago
No it isn't. My original point is that Latin-1 is used very rarely on Internet and is being phased out. Now it's your turn to provide some references that a significant percentage of websites are omitting encoding (which is requir
83.
by ko27 3y ago
But where do you find it? Almost the entirety of internet is UTF-8. You can always transcode to Latin 1 for testing purposes, but that raises the question of practical benefits of this algorithm.
84.
by ko27 3y ago
> so you don't get the HTTP default of Latin-1. That's not what your linked spec says. You can try it yourself, in any browser. If you omit the encoding the browser uses heuristics to guess, but it will always work if you write
85.
by ko27 3y ago
Since HTML5 UTF-8 is the default charset. And for headers, they are parsed as ASCII encoded in almost all cases although ISO-8859-1 is supported.
86.
by ko27 3y ago
> Latin 1 standard is still in widespread inside some systems (such as browsers) That doesn't seem to be correct. UTF-8 is used by 98% of all the websites. I am not sure if it's even worth the trouble for libraries to implement
87.
by ko27 3y ago
What are you talking about? Galileo is a big win for the EU, even after taking into account the initial problems.
88.
by ko27 3y ago
Entropy is very much "real" and it exists outside of our mind. The resolution to Maxwell's demon is that knowledge of every particle's state is not free, you need to increase the system's entropy by obtaining knowle
89.
by ko27 3y ago
The simple reason is that if you design your language with limitations of a quantum computing you can make certain guarantees about your program being able to physically execute on any quantum computer. You can find more details here: http
90.
by ko27 3y ago
> Unfortunately, this color cannot be represented with CSS colors (rgb(999,999,999) doesn’t work) I think this is wrong. Browsers already support HDR with other color space like this one https://oklch.com/

More ›