FlorianRappl

I just saw three dependencies (arguably even less): https://www.npmjs.com/package/react

Don't know how you reach your conclusion.

smapiot | SW Architects and SW Engineers | ONSITE | Full-time | Munich, Germany

smapiot (https://smapiot.com) is a young startup focusing on premium IT consulting and engineering software services in the IoT / development tooling space. For smapiot the bread and butter business is the development of cloud native applications featuring reliability, scalability, and security. Our consulting projects touch a broad functional spectrum including identity management systems and smart home platforms.

Our technology stack includes C#/.NET, TypeScript/React, Azure, K8s, Docker, Mongo and many more interesting and leading-edge technologies. Essential to us is a friendly and collaborative working environment which fosters a constructive and open discussion culture, while working in an agile and flexible way tailored to our needs. Within smapiot everyone has a tech background and we are proud of our experienced architecture team. Regularly we meet up in joint retreats, general tech discussion sessions, or other team activities.

We are looking for skilled full stack web and backend developers who are keen on building amazing tools and state-of-the-art solutions. If you have some work experience in Europe and are attracted by the vision of contributing to the growth of a young, innovative company, then don't hesitate to apply via StackOverflow at https://stackoverflow.com/jobs/272468/software-engineer-for-....

If its a config file I'm not sure why you'll need comments. Comments / documentation should be in the system you'll do the config for. If your set options are that quirky / need documentation; why not explain them in a README?

But maybe I misunderstood. Can you give an example of a comment that makes sense / is required in a configuration JSON?

To this day I am baffled why choose YAML? Personally, I think its more error prone, less flexible, and harder to read than JSON. Not to say JSON is a perfect format, but it sure feels better than YAML.

... in a table / page called "Languages".

Wait until you spot Wordpress in the list, too.

I will never understand why tech companies suddenly let non tech people step up as CEO.

It always failed (failed = does not continue on the same trajectory; at best is stable and in the long term eaten up by more innovative companies).

I don't expect the C# compiler to understand F#, but in my opinion there should be language independent ways to create CLR assemblies. MSBuild (which calls the right compiler for each project) could also understand (and did iirc) compiler-independent project types that still produce assemblies, however, from mixed sources. Now the C# compiler would only be called for the C# sources.

> Basically a single assembly has to be written in the same language.

This is like saying a single js file has to come from only js files, still bundlers today merge all kinds of types in there - in a single sweep.

I am not writing this since I think mixing C#/F# is the future (well, it would be cool), but because it could allow the C# ecosystem to improve. Right now the best thing we have for metaprogramming in C# is Fody; and I personally think we could do better.

Hopefully this expressed my idea a little bit better.

That's not the root of the problem. Personally, I wish MSBuild would be more powerful and would allow mixed compilation where some files are in C#, some in F# (or VB.NET or some other language targeting the CLR).

Right now most companies (in the .NET world) just run on C# and no one tries anything new except when it arrives in C# (and even then its a struggle - even though the situation has improved a lot in recent years). A mixed model would also open other scenarios.

The mixed compilation is something that current web tech (using bundlers) has in advance. I can do crazy things and end up with the best (optimized) output using a common denominator.

On the F# track I fully agree - its a wonderful language that more people should try out.

smapiot | SW Architects and SW Engineers | ONSITE | Full-time | Munich, Germany

smapiot (https://smapiot.com) is a young startup focusing on premium IT consulting and on engineering software services in the IoT and development tooling space. For smapiot the bread and butter business is the development of cloud native applications featuring reliability, scalability, and security. Our consulting projects touch a broad functional spectrum including identity management systems and smart home platforms.

Our technology stack includes Elixir, C#/.NET, TypeScript/(Node.js and React), Azure, Kong, K8s, Docker, Mongo and many more interesting and leading-edge technologies. Essential to us is a friendly and collaborative working environment which fosters a constructive and open discussion culture, while working in an agile and flexible way tailored to our needs. Within smapiot everyone has a tech background and we are proud of our experienced architecture team. Regularly we meet up in joint retreats, general tech discussion sessions, or other team activities.

We are looking for skilled full stack web and backend developers who are keen on building amazing tools and state-of-the-art solutions. If you have some work experience in Europe and are attracted by the vision of contributing to the growth of a young, innovative company, then don't hesitate to apply via StackOverflow at https://stackoverflow.com/jobs/272468/software-engineer-for-....

Important: Emails from recruiters and spam factories will be ignored.

People sometimes mix up microfrontend with "running multiple frameworks". Its not the same. Actually, the main difference between microfrontends and microservices is that microfrontends should be written with an application shell and many (development) boundaries in place - otherwise the UX will be terrible and hard to get consistent.

Disclaimer: I am one of the people behind Piral (https://piral.io) which is a microfrontend solution based on React.

I fully agree, that's why we created "Piral", which is microfrontend solution that advocates using a single UI library (React). Of course, it also allows running multiple frameworks (such as Angular or Vue), but they are opt-in and by default people should just use a single one.

I fully agree. I also did not see any evidence. Very confused about this whole thing now...

Sorry I'm too stupid for this one.

Who wrote (or said) something about what or which person? Was the indicated talk the target here? Was the person giving the talk the target here? Who was attacked and why?

On the surface that just seemed that the majority of the people contributing to some project (in this case React) are white people which presumably ends up in joining together and dismissing opinions coming from people associated with other groups. Was this the case? Where is the evidence for that? Is / was the discussion completely unrelated to this? Really - I don't get at it all. Maybe a language barrier.

Don't get me wrong - if something like that occurred then a CoC / actions from the project leads must follow, but I just don't see it. Maybe the article is not clear about it.

Thanks for helping me out on this one!

smapiot | SW Architects and SW Engineers | ONSITE | Full-time | Munich, Germany

smapiot (https://smapiot.com) is a young startup focusing on premium IT consulting and on engineering software services in the IoT and development tooling space. For smapiot the bread and butter business is the development of cloud native applications featuring reliability, scalability, and security. Our consulting projects touch a broad functional spectrum including identity management systems and smart home platforms.

Our technology stack includes Elixir, C#/.NET, TypeScript/(Node.js and React), Azure, Kong, K8s, Docker, Mongo and many more interesting and leading-edge technologies. Essential to us is a friendly and collaborative working environment which fosters a constructive and open discussion culture, while working in an agile and flexible way tailored to our needs. Within smapiot everyone has a tech background and we are proud of our experienced architecture team. Regularly we meet up in joint retreats, general tech discussion sessions, or other team activities.

We are looking for skilled full stack web and backend developers who are keen on building amazing tools and state-of-the-art solutions. If you have some work experience in Europe and are attracted by the vision of contributing to the growth of a young, innovative company, then don't hesitate to apply via StackOverflow at https://stackoverflow.com/jobs/272468/software-engineer-for-....

I also see this use case.

Why? Ongoing "battle" between a large CMS (AEM) and a more modern SPA using microservices. Our claim is that the SPA is actually a superset of everything. It can SSR (like the CMS), it can also get data to display (like the CMS). All that is missing is a service for such data (we have other services delivering domain specific data).

Now the problem is not in a data service, but rather in the whole infrastructure around it - to make it easy for an content editor to use. These people like drag and drop and they would love your solution.

Great job!

Anyone else noticed that the page is constantly doing some requests to log the users behavior, e.g., on scroll? Also some of these requests (always?) fail.

Was annoying as the page did some jumps on these requests and the icon indicated the loading activity. If you have to do - do it in the background.

You should not store any token in the frontend. Instead, have a server doing that and use a classic secure cookie session. The session is bound to the token / refresh token and can then do the token management.

Alternatively, don't use access token / refresh token but an ID token. The refresh of the token will be done via the ID token and the user's session (cookie) to the OAuth provider.

smapiot | SW Architects and SW Engineers | ONSITE | Full-time | Munich, Germany

smapiot (https://smapiot.com) is a young startup focusing on premium IT consulting and on engineering software services in the IoT and development tooling space. For smapiot the bread and butter business is the development of cloud native applications featuring reliability, scalability, and security. Our consulting projects touch a broad functional spectrum including identity management systems and smart home platforms.

Our technology stack includes Elixir, C#/.NET, TypeScript/(Node.js and React), Azure, Kong, K8s, Docker, Mongo and many more interesting and leading-edge technologies. Essential to us is a friendly and collaborative working environment which fosters a constructive and open discussion culture, while working in an agile and flexible way tailored to our needs. Within smapiot everyone has a tech background and we are proud of our experienced architecture team. Regularly we meet up in joint retreats, general tech discussion sessions, or other team activities.

We are looking for skilled full stack web and backend developers who are keen on building amazing tools and state-of-the-art solutions. If you have some work experience in Europe and are attracted by the vision of contributing to the growth of a young, innovative company, then don't hesitate to contact us by writing a mail with your CV to recruiting@smapiot.com.

Important: Mails from recruiters and spam factories will be ignored.

When I saw this example I knew that this isn't for me. Super verbose and the arguments in favor of OOP are shallow at best.

If it would be 2013 the "hacky" way would be acceptable, but JSX is a de-facto standard that is supported by all tools used in production (incl. TypeScript, Babel, your favorite colorizer, language server extensions, ...).

Imho the proposed way sacrifices readability a lot (what does "with" do? is it like the infamous JS with? what is the first, second, third, ... argument?).

I appreciate the trend to break the frontend monolith - I think its one of the next steps for grand scale web apps. However, that noted this is certainly not for everyone and it has some downsides (e.g., complexity) that need to be tackled.

Right now there is also some lack on tooling and framework / library side. Nevertheless, there are some approaches already.

A project currently in the making is Piral (https://piral.io). It is not production ready at this point, but I think it may hit some sweep spot depending on your requirements (see https://github.com/smapiot/piral/blob/master/docs/features.m... for features and comparison to other / similar frameworks for micro frontends).

Disclaimer: I'm one of the authors.

I thought the same ... I think it actually is the same.

smapiot | SW Architects and SW Engineers | ONSITE | Full-time | Munich, Germany

smapiot (https://smapiot.com) is a young startup focusing on premium IT consulting and on engineering software services in the IoT and development tooling space. For smapiot the bread and butter business is the development of cloud native applications featuring reliability, scalability, and security. Our consulting projects touch a broad functional spectrum including identity management systems and smart home platforms.

Our technology stack includes Elixir, C#/.NET, TypeScript/(Node.js and React), Azure, Kong, K8s, Docker, Mongo and many more interesting and leading-edge technologies. Essential to us is a friendly and collaborative working environment which fosters a constructive and open discussion culture, while working in an agile and flexible way tailored to our needs. Within smapiot everyone has a tech background and we are proud of our experienced architecture team. Regularly we meet up in joint retreats, general tech discussion sessions, or other team activities.

We are looking for skilled full stack web and backend developers who are keen on building amazing tools and state-of-the-art solutions. If you have some work experience in Europe and are attracted by the vision of contributing to the growth of a young, innovative company, then don't hesitate to contact us by writing a mail with your CV to recruiting@smapiot.com.

Important: Emails from recruiters and spam factories will be ignored.

Reality is that a password expiration policy quite often leads to password simplification (e.g., having an incremented number in the password, post its on the screen, ...).

I'd prefer 2FA and (allowing / encouraging) longer / stronger passwords over change policies.

I interviewed with most of the "tech giants" and Microsoft's process was by far the best (professional and down-to-earth). Maybe this was due to the target (language team), maybe due to the location (Redmond), but at least with me they left a great impression.

This line also caught my attention. Really keen on finding out more!

smapiot | SW Architects and SW Engineers | ONSITE | Full-time | Munich, Germany

smapiot (https://smapiot.com) is a young startup focusing on premium IT consulting and on engineering software services in the IoT and development tooling space. For smapiot the bread and butter business is the development of cloud native applications featuring reliability, scalability, and security. Our consulting projects touch a broad functional spectrum including identity management systems and smart home platforms.

Our technology stack includes Elixir, C#/.NET, TypeScript/(Node.js and React), Azure, Kong, K8s, Docker, Mongo and many more interesting and leading-edge technologies. Essential to us is a friendly and collaborative working environment which fosters a constructive and open discussion culture, while working in an agile and flexible way tailored to our needs. Within smapiot everyone has a tech background and we are proud of our experienced architecture team. Regularly we meet up in joint retreats, general tech discussion sessions, or other team activities.

We are looking for skilled full stack web and backend developers who are keen on building amazing tools and state-of-the-art solutions. If you have some work experience in Europe and are attracted by the vision of contributing to the growth of a young, innovative company, then don't hesitate to contact us by writing a mail with your CV to recruiting@smapiot.com.

Important: Emails from recruiters and spam factories will be ignored.

Such a guide can be reduced to:

If you only have a single file that has a limited set of responsibilities (e.g., just a small tool) and is not shared / distributed then JS may still be okay, otherwise always go for TypeScript.

Honestly, TypeScript never slows me down. The enhanced completion / IDE knowledge, compile-time type checking, and transpilation supporting newer ES features + React is a huge boost.

smapiot | SW Architects and SW Engineers | ONSITE | Full-time | Munich, Germany

smapiot (https://smapiot.com) is a young startup focusing on premium IT consulting and on engineering software services in the IoT and development tooling space. For smapiot the bread and butter business is the development of cloud native applications featuring reliability, scalability, and security. Our consulting projects touch a broad functional spectrum including identity management systems and smart home platforms.

Our technology stack includes Elixir, C#/.NET, TypeScript/(Node.js and React), Azure, Kong, K8s, Docker, Mongo and many more interesting and leading-edge technologies. Essential to us is a friendly and collaborative working environment which fosters a constructive and open discussion culture, while working in an agile and flexible way tailored to our needs. Within smapiot everyone has a tech background and we are proud of our experienced architecture team. Regularly we meet up in joint retreats, general tech discussion sessions, or other team activities.

We are looking for skilled full stack web and backend developers who are keen on building amazing tools and state-of-the-art solutions. If you have some work experience in Europe and are attracted by the vision of contributing to the growth of a young, innovative company, then don't hesitate to contact us by writing a mail with your CV to recruiting@smapiot.com.

Important: Emails from recruiters and spam factories will be ignored.