Isn't Playwright a testing framework, I am not sure how this solves the use-case that Onedoc is aiming for.
I would be highly interested in some more background as we are evaluating alternative solutions to princeXML right now.
Did anybody else face the issue that they got a mail from Microsoft asking them to "Try Designer" however once you try to login with your account it mentions: This account doesn't exist.
I am not sure what Designer is and I wanted to check if it was a Figma/Adobe XD competitor.
I did get the email too, but didn't have the issue.
From another comment of mine:
> It is not a Figma alternative. Figma is a tool for designers to design. Microsoft Designer seems to be a tool for non-designers to attempt design, with the help of AI. Very different audiences, and trying out the tool, everything about the UI/UX makes that very clear, Microsoft Designer is more like a wizard for creating a initial design, while Figma is a proper tool.
Yeah, I guess its still a no-Go due to the botched addon support in the regular Android Firefox build ? But maybe in the Nigtly/Beta using that annoying addon list trick ?
I'd love to hear more about replacing tomcat. Can you lead me to some info material on that topic. In our company we rely heavily on application servers, faster alternatives are always worth checking out.
Sure. Let me try to share some details. But before that, just want to make a point (which you surely know) that its also a major decision of a language change from Java to Go.
In the Tomcat/Jetty/<any other Java app server> world. If we want to have a web app (HTTP) we need to code servlets and add them into web.xml config, matching urls to Servlet Names. And within the Servlet we have coded, we need to call other Java code (the logic).
The container/app server takes care of the TCP/HTTP layers. Thread pools (which you can configure etc.).
Now in the Golang world. We just use the http package[1] for all that.
To listen to url:
http.Handle("/doSearch", &MySearch{"MySearch"})
Where MySearch is a struct which just needs to implement the interface:
func ServeHTTP( w http.ResponseWriter,r * http.Request)
Within this function you can put all the code which you will put in a java Servlet.
And to make this a service in your main package/program you will also do:
So these 3 pieces are the ones needed to have your own micro service or any web service running.
In our case, the similar functionality when moved resulted in lower memory usage and much higher stability (very less crashes, in the rare event of the service needing memory, which OS doesn't have. So the OS will kill that service anyhow - tech independent. We check using dmesg | grep <program name>)
Another benefit of this move, from our experience is getting rid of that webapp folder in any Java Servlet container. You will often end up plugging along multiple smaller apps, alongside your main one. And all reside in the same process.
That's not ample segregation, in our use. Its better you have different processes. So even if one dies, the others are independent.
This is also easier to manage. Deploy new ones - restarting just the ones changed.
Now we all know hot loading (without restart) is offered in several techs including some Java containers. But in practice, there always is some silly reason for you to restart. And sometimes the reason is psychological :-), we are not convinced that there is some baggage until we restart.
So hope my brief experience share is of some use. All the best.
Edit: Just want to add You must review this package page, if you are considering it
I really love Soundcloud but the "Shuffle" is the only thing I don't like. I am actually planning to design a small single-page one-purpose site for exactly that: A real Shuffle for Soundcloud!
