woumn

I'm working on a visual watchface builder for Garmin smartwatches currently. Think like Canva but for a watchface. It's not released yet, but coming along well. I'd like to support other brands too, like Pebble.

I think this is awesome. I'd love to see alternatives to React for the SSR. Potentially a Ducklang UI library so I don't have to write divs and useState()

I am thinking you opened an issue. Thank you! I added one.

It would be possible, but I don't have a good ldap server to test on, especially one I can modify config changes. If you'd like to contribute to the repo, adding a test ldap server that can be used for development would enable a lot more features.

Haven't tested, but i think it should. it's using Go's LDAP library in the background

I don't have a way to debug windows, so atm it's kind wysiwyg.

#2 is a great idea. open a ticket if you'd like.

I hate it so much. And it barely works with newer macs.

Will do!

You're very welcome!

Thank you!

The lack of integrated terminal or method of running a go program makes me question what use this is to someone. Until either of those is implemented, this is a no-go for me. Not even mentioning that it costs money to use without adding any value over free editors.

I went to school at K-State and was best friends with one of the original developers of this software. Eventually, I took a formal logic class with a professor in the philosophy department, Graham. He is involved to a large extent in this as well. One of the best professors I had—-incredibly intelligent and patient and all around good.

I would highly recommend people check out Carnap. Having used Z3 and Alloy in other classic, Carnap was by far the best one I used. Very fast and it gave actually useful error messages. It was also so cool how it could represent different types of logic systems. The whole thing is like a cool blag magic to me.

That's interesting. That fix seems unreasonable for me considering I already have difficulty reading on screens. But that's at least a point to look for later on in the release notes.

Which is so surprising to me because it's using the HTML5 video player and toggling around with hardware acceleration does nothing to fix the issue. Perhaps it's the integrated chat + any of the add ones that Twitch has written for the videos?

I saw the same issues and I'm using a 2017 MBP 15" with the middle of the road CPU and 16GB RAM (dedicated GPU as well).

I use Opera as my personal browser and it handles video pretty well. It's running Chromium under the hood, and I don't think any major improvements have been made for video in Chromium or in any of the standards like HTML5 or flash. I see on par performance to stock Chrome.

Yea, most of my browser time spent during free time is strictly on Twitch/Youtube/Netflix. Until these see improvements, then I won't make the switch.

That sounds like the developers messed up some Javascript references that are unable to be cleaned up to me. But interesting nonetheless.

Could you please report back with your findings? I'm also terribly interested in this as well.

Out of curiosity, were these high CPU usages on pages with any sort of video playing (culprits for me were Twitch or any live stream)? I was also having these issues, and I want to use Firefox, but the performance in the past was just too difficult.

I always get so excited for new Firefox releases. Then I read the patch notes and never see that they've fixed performance for MacOS. I've tried everything I can find online, but Firefox just performs so terribly on my Macbook Pro. In the meantime, I use Opera (with little to no complaints).

I'd like to add in Cloudkicker, which sounds a bit different than straight Djent, but has gotten me through a lot of college.

Unfortunately, the update for Mac doesn't solve the battery usage issue.

So, I worked with ROS over the summer at my internship. If I could ask, what did your closed-source version improve on?

In my experience, one of my worst experiences with ROS was maintaining environments and python versions as well as the build system.

It turns out that my exploit did not work locally or remotely. I'd love feedback from you all if my understanding is flawed.

I would suggest reading at least through to "What's Happening?" because I show that at least my exploit attempts to run the shell code, but the actual shell code throws an exception!