๐ Exciting news from SelectView Data Solutions! ๐
We're thrilled to join the #fsharp community. Today marks our first contribution: Elmish Store, a library blending #elmish with #react for efficient state management in F# apps.
Explore it here: https://t.co/Z8e1yzM6G9
After almost 5 years with my current client, I am now open again to new opportunities. If you're looking for a #remote#fsharp#csharp#dotnet#azure#cloud dev with experience in payments, banking, e-commerce and ERP then feel free to contact me via DM.
After almost 5 years with my current client, I am now open again to new opportunities. If you're looking for a #remote#fsharp#csharp#dotnet#azure#cloud dev with experience in payments, banking, e-commerce and ERP then feel free to contact me via DM.
@pavsaund Thanks Pav. Looks like it's mostly server maturity and availability at this moment. I went with https://t.co/bYSoqhDvg2 for now, may or may not move somewhere else in the future ;)
I'm really not a fan of read-reciepts and "X is typing" prompts in chat-based communication in general.
For me it removes the async nature of reading, reflecting and composing a response from the experience
It's led to so many sub-par message exchanges.
@thereformedprog I guess if the projects will be pretty small and the dependencies would be properly managed then it should work fine from the VS side (although the performance may deteriorate quite a bit sometimes). What I expect to be severely impacted is server build time.
Would tons of small #csharp projects basically mean one project in #fsharp dependency-wise? You would have to manage the order of the projects the same was as the order of files/dirs in F# - probably the most love-hate property of the language?
Does anyone know how many projects you can have in Visual Studio 2019 solution before it gets hard to work with? Please reply
I ask as I have a Modular Monolith pattern (https://t.co/fVU0WaHmGu) that uses lots of small projects. In in a real app this could get up to 500 projects
Unless there are separate deployment units I would say one large project with multiple (maybe even nested) folders would be easier to work with; the downside would be that you have to build the whole project every time while with small ones you only have to build the changed ones
@tomasekeli That's a shame that so many places still require this, and it's making new ones do it as well to be able to interact with the ones that force it already. It's so common that it makes doing things right in any new system extremely difficult unless you have no integrations at all.