351–359 of 359 posts
Not really relevant but I need to vent. Client dropped Slack for Teams. I hate it, and information exchange has dropped precipitously since everyone switched. So slow, half the time text markup doesn't work, and the UI is inconsistent depending on if you're typing in a chat, meeting, or channel. Oh and none of the Slack logs were kept, losing years of information. (But that's not the fault of the Teams software) I lo…
Earlier quoted context omitted.
In other words: outdated, ugly and barely supports modern requirements such as high dpi. Apart from Jetbrains who put in a literal buttload of engineering, there is not a single Java Swing application that is not an absolute PITA to use.
Swing generally looks like the native widgets set. And how is it outdated? It's not like GUI programming has changed much.
It's very frustrating that a company of that size and tech 'prestige' can't make native apps and instead rely on these crutches like Electron. The difference is very noticeable in the user experience.
Not really relevant but I need to vent. Client dropped Slack for Teams. I hate it, and information exchange has dropped precipitously since everyone switched. So slow, half the time text markup doesn't work, and the UI is inconsistent depending on if you're typing in a chat, meeting, or channel. Oh and none of the Slack logs were kept, losing years of information. (But that's not the fault of the Teams software) I lo…
Company decides the most important thing is to save $20 a month on not paying for slack
Not sure what everyone issues are. I use Teams (in the browser) on Linux and it works fine under both X11 and Wayland (with some work). A bit less polished than Slack but it also has a lot more features. The worse thing about the desktop/Electron version is that they are really bad about keeping the electron version updated so the browser version will support screen sharing on Wayland while the desktop app doesn't.
In my experience, most people in engineering orgs default to hating Teams far more than it deserves. and loving Slack far more than it deserves. This has roots in Microsoft's history as computing Bad Guy and Slack's pre-Salesforce history as Scrappy Indie. Teams is more complex than Slack but also does more, but it's also not a complete superset of Slack, so unplanned/unguided transitions from Slack to Teams tend not…
Perhaps that's the problem. I generally prefer the right tool for the right job, and once I have a tool that works, the effort to switch needs a compelling reason.
Adding a "hammer" function to a screwdriver makes the screwdriver worse, it doesn't provide that compelling reason.
Adding multi client access, stored chats, and even some formatting, were compelling reasons to switch to slack over irc.
Earlier quoted context omitted.
Yep, we moved away because MS themselves are simply not serious about it.
Cross-platform development is like communism. An unattainable utopia. There's no "magicking-away" the idiosyncrasies of cross-platform development with abstraction layers. It's simpler to use native tools and go for the best each platform has to offer while keeping the L&F UX as similar as possible.
Earlier quoted context omitted.
It looked interesting to me, but their disnhonesty just threw me back: > Not a subscription—never expires > Includes 1 year of free version upgrades Are you telling me that a third-party slack client will keep working forever without updates? The "not a subscription" message here is effectively moot: this thing will stop working and you will need to pay for "another year of version upgrades".
Those are the two common models of proprietary software distribution - subscriptions or one-off payments. Did you actually expect lifetime updates for $20 - i.e. the benefits of subscriptions for the price of one-off purchase? It's not promising you to work forever without updates, but also it doesn't force you to pay if you're happy and everything still works.
Contrast this with something like sublime text: years from now you can still expect it to work normally.
What I expect is that if your app will not continue working for a long time then you should not make "lifetime license" one of your selling points unless you are prepared to offer lifetime upgrades too.
Earlier quoted context omitted.
Swing generally looks like the native widgets set. And how is it outdated? It's not like GUI programming has changed much.
I‘m sorry but have you been living under a rock? SwiftUI, UWP and Jetpack Compose are platforms that differ extremely from the way Swing works. Swing on macOS looks like OS X 10.9 (still uses Lucida Grande as the System Font), we’re 5 releases past that. On Windows, it looks like Vista, we’re past that, too, see modern apps such as the Terminal.
I just opened a couple of Swing programs on macOS. Other than not having dark mode, I couldn't see any major difference. I can't check it on Windows right now.
So, no, I don't live under a rock.
Earlier quoted context omitted.
It's because they control the whole stack. FWIW, I'm currently finishing up an ActiveX wrapper for WebView2 so that it can be consumed in a way similar to the old IE WebBrowser control and so far I'm pretty impressed. To give you a basic idea. I'm running the control embedded and the WebView2 control consumes about 60MB after navigating to my own -mostly text- website. Browsing within that control to the page of the…
> I'm currently finishing up an ActiveX wrapper for WebView2 so that it can be consumed in a way similar to the old IE WebBrowser control and so far I'm pretty impressed. To what extent are you maintaining compatibility? The old mshtml provides com bindings for pretty much everything. I'd be interested to see what you have if you end up releasing the code. I would love for the old Trident / mshtml / edgehtml engines…
The demo application is currently only in DataFlex, but I will add other programming languages for the demo later on.