Notably, SendGrid went through the Techstars accelerator instead. One of their mentors from the Techstars program [1], Jim Franklin, later became SendGrid's CEO and helped the technical founders grow the company towards the success they eventually achieved.
Actually, the compiled JS is `React.createElement('mesh', { ref: mesh } )`. JSX compiler converts all lower-case names to strings. Only upper-case name (and composites like `rn.View`) are converted to variables.
The reason r3f uses lower-case names for built-in components is to distinguish them from your own components; from the documentation: "It merely expresses Three.js in JSX: <mesh /> becomes new THREE.Mesh(), and that happens dynamically." So whenever you see <mesh /> or anything else lower-case it is just an JSX alias for a Three.js core component. Note that they're not HTML tags in the resulting output; since they're rendered inside <Canvas />, they're transformed to Three.js automatically.
There are similarly magic numbers in the database cost. A 2 vCPU/4GB instance is db.t2.medium which comes to about $35/month on demand, plus 120 GB is addt'l ~$13 so it actually comes out cheaper than the lightsail version, and certainly way below the proclaimed $200.
"Learn once, write everywhere". Can't speak about performance comparison vs using Qt/.NET/whatever but the whole idea about React Native is that today, you can write a native app for iOS, tvOS, Android, web, macOS, Windows, and a few others, all using the same language and framework. You still have to understand platform specifics like UX guidelines but you use the same technology to build a fully customizable, and fully performant, native experience. It's sort of like using C++ but way more developer friendly.
The cons:
- an extra layer of abstraction
- need to write a plugin if you want to surface a native functionality to RN if it's not yet supported
- no visual UI editor like in native tools (Qt/VS), although you generally won't need it with React Native's code-first and instant refresh development workflow
- you need to be comfortable with React Native / JavaScript, obviously :-)
It's not gonna run everywhere, for the same reason WPF doesn't run everywhere. Given that the apps written with this will bind to Windows using C++, and there is no abstraction in between (like Qt), it's not gonna be portable. As far as I understand, it is going to be a reimplementation of React Native where the apps might have a similar style, but the backend will be completely Windows specific. And nothing will stop a developer from using native Windows APIs, so they will.
> The "current" subdirectory adds support for an earlier React Native for Windows10 implemented from scratch in C#. It reimplemented the JS<->Native bridge in C#, and shared the JS with Facebook's implementation of React Native. The ongoing direction of React Native involves a closer interaction between C++ and JS which is hard to achieve with a separate C# implementation.
Given that they say that the "old" version "shared the JS" in past tense, that seems to hint that the "new" version will not share the JS? In that case, what is left of React? It sounds like it will be the same style of API and workflow, but different widgets and no cross-platform compatibility.
You can also write a native app for Android/iOS/tvOS/Windows/macOS/Linux and a few others, all using the same language and framework - C++ and Qt - see: https://doc.qt.io/qt-5/supported-platforms.html
There have definitely been a number of students admitted to the GT's OMSCS program who didn't have an engineering undergraduate degree. Not sure though what are the stats of students without any bachelor's degree at all...
There is a requirement to complete a few foundational courses after you enroll but you still need to be accepted first.
Intro to Information Security, for example, has four hands-on projects:
1. Exploit a buffer overflow in a C program
2. Use Cuckoo to understand a malware attack
3. Implement CBC encryption algorithm and a brute-force algorithm to crack it
4. Demonstrate an XSRF, XSS and SQL injection attack
Remember this is an intro course and there are about 2-3 weeks per project so you won't be an expert but I'd say it makes you aware of some of the basic security attacks and how to prevent them.
Very cool! I actually considered building something similar myself about a year ago but got pulled into other projects... definitely see a lot of value in providing a single interface.
How are you planning to handle the explosion in complexity? Once you have hundreds/thousands of different services integrated, the schema becomes rather huge, especially if a specific user only needs a fraction of it. Is the plan to toggle services on/off and then only stitch the schema for a particular user with the limited set of fields?
Flex is a company on a mission to make at-home bodyweight exercise as exciting as boutique studio classes. We combine wearables like Apple Watch with live video workouts to deliver a fun, immersive, gamified fitness experience that quickly becomes addictive.
> you really have to do a lot of work on your own in order to be competent in a specialization
Totally agree with this. For courses like AI, ML, and RL, I watched lectures from Berkeley and Stanford in addition to the GT lectures, and that really helped me understand it better.
> get a well rounded overview of some modern trends in cs
That's usually the case for a master's. PhDs are more in-depth.
[1] https://davidgcohen.com/2020/09/19/a-review-of-the-first-ele...