191–200 of 209 posts
Earlier quoted context omitted.
> I call it out as weird because take SwiftUI for example, the main excuse Apple engineers gave for why SwiftUI itself is closed-source is because a lot of important code lives inside of UIKit/AppKit. Huh?! SwiftUI is just a closed source framework. What's so confusing here? We don't expect Microsoft to develop its proprietary APIs out in the open despite it having a large presence in the open source world, why would…
> We don't expect Microsoft to develop its proprietary APIs out in the open despite it having a large presence in the open source world, why would we of Apple? .NET is fully open-source now and it is developed in the open. And not just the BCL, but also platform UI/UX libraries like [WinForms]( https://github.com/dotnet/winforms ) and WPF. (Yeah I was taken aback too: if you told myself from 10-15 years ago that WinF…
Earlier quoted context omitted.
It's pretty clear that since Chris Lattner left Google the Swift Tensorflow version isn't really going anywhere.
They are still paying a bunch of expensive devs to work on it, so maybe not.
That's lost in the TensorFlow team budget.
Earlier quoted context omitted.
Flutter is probably the best candidate. It's a shame Google is giving priority to Flutter for Web instead of desktop though. As discussed previously here on HN, Flutter for Web will always result in bloated web apps as they are reimplementing everything through canvas (eg: text editing, layouts, styling, etc).
Quick note here: we're investing in both pretty heavily. Google has a fair amount of pedigree on the web, so it's highly attractive to us to have web support, but we're paying close attention to the attention that desktop is receiving and are accordingly putting resources on it. More news tomorrow, but see, for example: https://www.windowslatest.com/2020/09/21/google-flutter-uwp-... (Disclosure: if it's not obvious,…
Earlier quoted context omitted.
For a language compiling to native instructions, there's really only the C(++) API. UWP is barely used in my experience and WPF/Windows Forms are basically exclusive to the dotnet framework. Windows Forms and the native API share most of their controls' look and feel while WPF is a free-form application framework that allows you to ignore all UI standards if you desire to. I can't remember the last time I've seen a W…
UWP is so last year! We're all about WinUI now! ;)
https://microsoft.github.io/microsoft-ui-xaml/about.html
> WinUI 3 is the next version of the WinUI framework, shipping later this year. It dramatically expands WinUI into a full UX framework, making WinUI available for all types of Windows apps – from Win32 to UWP – for use as the UI layer.
Earlier quoted context omitted.
SwiftUI being closed source is a huge issue for developers. Apple behaves as if every user is immediately on the latest version but the reality is the _lucky_ developers support one major version back. SwiftUI is broken in completely different ways for each minor release of iOS 13 and none of the fixes in 14 are possible to use in 13. It's shocking how mismanaged the SDK development at Apple is.
SwiftUI is an attempt to stop the spread of people coding for things like React and instead focus in a Apple only SDK so they accomplish their goals of developer lock in. Knowing why Apple is doing this is important to understand why this will never happen. Apparently the feature they are using is function builders (1) and its already working on the current versions of Swift. So at least now, nothing is preventing ot…
Function builders are still not a public feature, and therefore subject to breaking revisions without warning.
Swift for Android would be a real milestone. There are not so many mainstream cross mobile development platforms.
Earlier quoted context omitted.
Swift on a server is a think: https://vapor.codes
The docs are very incomplete and common third party dependencies are missing. I know it’s a chicken and egg type situation but vapor is not an appealing option for backend unless you really want/need to use Swift.
Earlier quoted context omitted.
What I was trying to say is why should Apple port Swift to Windows? They have to prioritize resources and Windows should be way down near the bottom of the list. It’s easy to say Apple has nearly infinite amounts of resources, but that never true in the software business. Someone has to manage the project, hire/manage teams, make decisions on goals, objectives, and they have to be managed by someone in engineering le…
> They have to prioritize resources Hence pjmlp wrote: "Poor Apple, budget cuts have been hit really hard". I think that's entirely fair. Apple's resource is not infinite, but it's certainly more than enough to port Swift to Windows. Hence pjmlp says it shows "how important this is to Apple", especially in comparison to Java (Oracle) or .NET (Microsoft). I tend to agree.
Swift has this weird sort of ecosystem where Apple builds much of the platform in a very secret (most of the roadmap isn't shared), closed-source variant for its own OS. Then it has this open source version, with a very public compiler (roadmap IS shared) that allows cross platform toolchains like this one to exist. I call it out as weird because take SwiftUI for example, the main excuse Apple engineers gave for why…
Swift manages to be technically open-source while not really being true to the idea of open-source. To me, it always seems as if somebody at Apple saw that companies like Microsoft going open source was good publicity and decided that they should do it now too, without really understanding what "open source" means. Some examples of this IMHO include: - While Swift itself is open-source, "Foundation" (which is somethi…
Which parts of the generics manifesto are "properly fixing generics" in your opinion?