Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
migueldeicaza
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
31.
▲
by
migueldeicaza
4y ago
The SQL comparison is a great illustration
32.
▲
by
migueldeicaza
4y ago
This is nonsense.
33.
▲
by
migueldeicaza
4y ago
That wasn’t the reason. Edge could just not compete with chrome, despite throwing hundreds of engineers at the problem. They tried, and tried, and tried. In the end “edge doesn’t work” was just code for “edge is not chromium” Electron was
34.
▲
by
migueldeicaza
5y ago
No, this will never be caught. This only catches ownership of illegal photos.
35.
▲
by
migueldeicaza
5y ago
There is a big stick coming from the EU (and someone said the same is coming from the UK). My guess is that Apple designed this privacy protecting system so that they could deliver the solution on their own terms - and perhaps leading the w
36.
▲
by
migueldeicaza
5y ago
Apple designed a new system, which is different than PhotoDNA - they call it neural hash, and the specifics are not disclosed.
37.
▲
by
migueldeicaza
5y ago
Apple's approach opens the door to get full end-to-end encryption for other assets that are currently stored on iCloud, that currently are not. It is not a guarantee, but it leaves that door open, which currently would face very strong
38.
▲
by
migueldeicaza
6y ago
It has been a while since I rebuilt the XNU kernel, a few years perhaps, but it is possible, and it works. These instructions are a lot better than the ones that I had to follow a few years back - I might try it, just need to find a guinea
39.
▲
by
migueldeicaza
8y ago
Reflection is the least of the problems this solves. The majority of the issues and gotchas listed in the generics FAQ for Java do not happen in C# at all. It is liberating. Reflection is an advanced use case that some people use, but it
40.
▲
by
migueldeicaza
8y ago
Neither Windows.Forms or WPF can easily be made portable, the code is really a thin layer on top of existing Windows services. I know, because I did this before with Mono, and the changes would be highly disruptive to the codebase.
41.
▲
by
migueldeicaza
9y ago
It is worth pointing out that when we dropped the interpreter, we only had two or three engineers working on the VM and they had to both develop the JIT and maintain the interpreter, plus work on the GC, io-layer and other VM features. With
42.
▲
by
migueldeicaza
9y ago
There are elements of truth in this, but it is not the whole story. While Silverlight did produce the first portable version of .NET and produces a lot of the code that allowed .NET to be portable, this code has been now retrofitted into th
43.
▲
by
migueldeicaza
9y ago
We now share a lot of code between the runtimes, it is an effort that we have taken seriously to improve compatibility, and capabilities. Today, when you checkout the Mono source code, it brings CoreRT and CoreFX. From a user perpective, we
44.
▲
by
migueldeicaza
9y ago
Just want to say, working with Unity and their team is a delight. And they have given great feedback on the future of the language and framework that Microsoft is going to fully embrace to make Unity users happy. Hugs and love Lucas!
45.
▲
by
migueldeicaza
9y ago
We are collaborating with Unity to assist on upgrading not only their runtime but also to adopt the latest and greatest GC. Additionally in C# 7, 7.1 and the upcoming 7.x series there are many improvements that reduce object allocation (lik
46.
▲
by
migueldeicaza
9y ago
That effort continues, we have an update in Mono's blog and we are about to share details on our next concurrent/parallel milestone soon.
47.
▲
by
migueldeicaza
9y ago
The code generator is indeed different, the runtime is still Mono. Mono today has two code generators: Mono's built it one, and an LLVM one. Both generate code after Mono loads and processes the assembly. Unity developed a different f
48.
▲
by
migueldeicaza
9y ago
We are now sharing code between the two stacks. This means that we get to share bug fixes, implementations and performance improvements. It is a process, and is generally going great. The challenge is tha Mono needs to ensure the larger
49.
▲
by
migueldeicaza
9y ago
Mono is focused on supporting mobile workloads while .NET core is focused on the server side. The class library implementations are converging (1) and some other bits are shared. Historically Mono has supported the "desktop" profi
50.
▲
by
migueldeicaza
9y ago
Android and iOS both use separate rendering processes/threads for UI and animation to eliminate a range of issues that would otherwise be observable. The code thread might hang, it scheduled rendering and animations will continue. The
51.
▲
by
migueldeicaza
9y ago
Please support us here: https://visualstudio.uservoice.com/forums/121579-visual-stud... It would be great if in addition to voting, you can articulate some reasons for why you care, add a personal touch, in the end, we
52.
▲
by
migueldeicaza
9y ago
Xamarin Studio users will be upgraded to Visual Studio for Mac ;-)
53.
▲
by
migueldeicaza
9y ago
Yes, MonoDevelop is still open source, it is still at the core of the system. Visual Studio for Mac is built as a series of components on top of the open source MonoDevelop. When we touch the core, it goes open source, and some of the exten
54.
▲
by
migueldeicaza
9y ago
We are under new management :-)
55.
▲
by
migueldeicaza
9y ago
We would like more people to speak up about this. We need your votes, your voices to make the case that we should release all this goodness on Linux. Little know fact: some of the engineers on the Visual Studio for Mac team are still develo
56.
▲
by
migueldeicaza
9y ago
Good guess. It is based on the MonoDevelop core with many new extensions to support new workloads (.NET Core, Azure Deployment, Unity development). Additionally, over the past year we have replaced started to replace the internals of MonoDe
57.
▲
by
migueldeicaza
9y ago
Yes, you can build .NET Core service apps. You can create new projects, debug them and bonus points - deploy directly to Azure.
58.
▲
by
migueldeicaza
9y ago
We will be adding support for more languages over time. Our focus for the initial release was to get our .NET Mobile, Cloud and Unity components in place. We have a solid pipeline of new features, stay tuned for more details on my Visual St
59.
▲
by
migueldeicaza
9y ago
I would like to add that we have been reusing a lot of the existing code from Visual Studio in Visual Studio for Mac. The code for Visual Studio is just incredibly well architected. It is a design jewel - the core components are independe
60.
▲
by
migueldeicaza
9y ago
Yes, we will be adding support for more languages. We will be doing that with the Language Server Protocol effort that was started at Microsoft and is currently in use by VSCode and other languages: http://langserver.org/ M
More ›