they'll end up preying on the people in 3rd world countries that don't have strong privacy legislation. Same way as Phillip Morris did with cigarettes...
I agree with almost all of the article. It brings up great points. The one thing I don't fully agree with is (2) Buy almost always beats build. I think generally it does apply and especially for unrelated, common pieces like feature flags or managed databases.
But I think there are plenty of cases when it makes sense to build rather than buy even when tools exist. 1) It helps build a muscle of getting things done. 2) It offers a way to learn new things and to try new things. 3) It gives you understanding and better control over the solution. If the saas goes out of service or out of business it can create stressful times trying to migrate at the last minute.
Graphs are usually persisted as a list of nodes and a list of vertices. The ML approaches usually use tuples or triplets of nodes to represent connectivity and model neighborhood. I wonder if that can not be used to model a graph in a linear system?
There are many reasons why I respect him, but the fact that he laid out a time plan for Scala 3 already 2 years ago and then kept the timeline is mind-boggling.
IIRC one of Odersky's stated goal for Scala 3 was to address exactly this issue. That being said, it is developed in a research setting so I guess even if they restrict these features now, there will be new ones added over time...
I’d argue it doesn’t make sense to fix c++. A language is not about what you can do with it, its about what it doesn't let you do. C++ will continue letting you do everything in the name of backward compatibility.
Wouldn't you say that the next logical step is to go up an abstraction then? Assembly -> C -> OOP/FP -> ??? In that case, wouldn't it make more sense if that abstraction was build on top of something which you can mathematically reason about?
I think the benefit of FP is long term. Refactoring and maintenance of systems somebody else, not with the company anymore, wrote. 2 months into a project you could be forgiven for thinking oop and fp are equivalent. You haven’t yet gone through a major shift in understanding the requirements.
Personally,I strongly prefer light libraries over comprehensive frameworks. Yes, you have to build up your app, but at least you understand what you're doing. And when something goes wrong you know how to fix it. You can follow the code. This is super hard with a framework like Django.
I don't think there is a conspiracy to suppress the information, but on the other hand I'd say EU has a long way to go in terms of PR and informing citizens. Somehow all these things always surface at 11:55
I found her sympathetic based on her statements about protection of democratic values in Poland and standing up for oppressed minorities in Asia. I haven't yet seen her bad side I guess.
I only have the problem with AirPod Pros. The fit test never passes in my right ear and they feel very uncomfortable after about 15 minutes. They also fall out when I speak and walk with them on.
But the worst is that sometimes my own voice resonates back in my ear, its hard to describe but very unpleasant and disturbing in a conversation.
Last time I checked it was not possible to actually use godoc to render the doc, it just started an internal server. That made it super hard to publish docs internally.
Personally I prefer being on the other end of the expression problem - where extending underlying data (mainly sum types) is the costly operation. Like in Rust, because it actually makes you think about the data model instead of the implementation. Adding new functions is "free" in the sense that it's not going to break your model.
But I'm curious if you don't find object algebras in Java cumbersome and kind of fighting the type system? Because while I like this kind of thing in Scala, in Java it feels very much against the design of the language.
I’d say when you run a big suite in CI and it takes an hour and your first assertion of many in a test fails, you don’t know if the others also fail or not. You fix it only to wait another hour for the tests to fail again.
It seems to me that this is only a problem when you try to write wasm directly. If you compile from rust then this analysis is already done for you on a higher level. or what am i missing?
I think Apple is in the “real estate”/rent business here. if you compare that to how big malls operate it’s pretty similar. They take a fixed fee plus a cut from the revenue in exchange for foot traffic.