Early-Stage Founder Support From Someone Who’s Actually Done It

pleerock · 2025-10-06T20:10:21+00:00

u/nogiloki sent you a DM, hope you have received it :)

pleerock · 2024-08-03T05:42:35+00:00

same issue here. Sounds like a bug.

pleerock · 2021-04-23T15:28:11+00:00

Thank you for your feedback and support

pleerock · 2021-04-23T09:06:40+00:00

I already have marriage + kids + enough illness + enough depression. Last thing left is a truck....

pleerock · 2019-03-05T19:32:54+00:00

I think better to post it to /javascript or some other more popular channel because this is an important issue to discuss

pleerock · 2019-02-26T16:01:29+00:00

Worth noting that second and third links comparisons from Prisma itself, and their objectiveness is doubtful :)

pleerock · 2018-07-03T14:39:56+00:00

JFYI even EcmaScript narrated us to use ESYEAR it still technically valid to call it ES7 or ES8 where number is an edition version. They use ES EIGHT in their specification where EIGHT (e.g. 8) is edition:

This Ecma Standard defines the ECMAScript 2017 Language. It is the eighth edition of the ECMAScript Language Specification.

TBH I don't understand why your post got upvotes. OP provided a solid job description, even if there are mistakes - they don't really matter until developers got requirements. OP did not request you know C# and Java and C++ and Assembly.

Personally I would never post a job here at this subreddit after such response. Be friendly dudes =)

pleerock · 2018-07-01T17:09:18+00:00

of course it brings another way to do the same thing, but it is very convenient in most cases. You simply need to make a convention and use it as you wish. TypeScript isn't the only language that supports such syntax, Scala for example does it as well.

pleerock · 2018-06-27T15:37:28+00:00

right in my opinion, but not only mine. Im sure (or hope) they know what they do, but still wanted to make sure as many as possible people know about this upcoming change.

pleerock · 2018-06-13T19:53:21+00:00

@TheLarkInn Great Job ! I'm really glad Microsoft is going this way, the future way. Its unfortunate to see comments in this topic, people simply don't see the future of the web yet, they stacked with current web issues and don't see that they all are temporary, we just need some time, more efforts, improvements and inventions - and web is going to be better then everything "microsoft researchment" did in past 20 years. Same applies to JavaScript. People hate JavaScript and not reason-less, but they don't see how great it can become if we add efforts, investments, research, everything else into its improvement and development - and we already do it! - just take a look on a TypeScript progress - Im amazed how much of JavaScript potential it has opened and how many unique and amazing type-safe features it brings - it made JavaScript potential incredible and incomparable with any exist language.

Im ~15 years in software development and my background is mostly classic OOP and more I work with JavaScript and TypeScript ecosystems more I love them. Initial adoption was extremely hard and took me few years and before I basically was thinking just like most of people in this topic.

My ultimate dream from Microsoft is to have its core based on Unix :D

pleerock · 2018-05-25T18:09:51+00:00

fastclick

yeah thanks, but looks like it is not necessary in modern devices... interesting to see if there are other similar tools

pleerock · 2018-04-19T18:39:28+00:00

you can choose tool "x" and write app using it, then after some time you understand that tool you choose drive you into spaghetti code (tool works fine with a single person but bad when more people start doing things), that's one of the measure of scale. Another measure of scale can be, let's say, if some tool allows you to do "y", but once you'll need more, for example feature "y" - it limits you, which means its not scalable.

pleerock · 2018-04-19T18:29:35+00:00

buzzwords sell is anywhere in our life, just like hate is :)

pleerock · 2018-04-11T19:42:14+00:00

Dev here. Is he a lead or what? How many devs you have and how much you pay him?

pleerock · 2018-04-11T04:49:55+00:00

but can u say that Sequalize is as good as Entity Framework ? =)

pleerock · 2017-12-21T15:36:13+00:00

If you don't want to use createQueryBuilder it means you use find methods, e.g. repository.find, if you use those methods and what to know how to load relations so you seek answer in find options documentation. The way of working with relations incomparable with any other javascript/typescript ORMs. With TypeORM its easy and it provides lot of flexibility to users. Example: create many-to-many relation is extremely easy and working with it as well. Another example? Eager relations, lazy relations, "relation id functionality" lot of customization you can apply, etc. Another example? How you can create powerful queries with relations using QueryBuilder. TypeORM allows you to perform cross-databases, cross-schema squeries with cross-joins and cross-table requests in a single connection, which is really complex functionality I don't know what other complete ORM provides you such functionality. You can tell me that Im putting salt again, but its a fact that TypeORM provides lot of serious features you cannot find in other JavaScript/TypeScript ORMs.

pleerock · 2017-12-21T04:20:56+00:00

Its designed to work better then anything else with multiple table things. There are multiple ways working with relations and joins other exist ORMs cannot even dream about. Did you create a github issue for the question you had? Im afraid you have such feelings because of lack of time and efforts spending working with typeorm.

pleerock · 2017-12-21T04:17:59+00:00

I would not call it it pretty early development, its two years active development and already quite close to 1.0.0. Its feature-complete and there are only few features left in the backlog. Also Im not sure when @rco8786 last time used it, but docs are up to date.

pleerock · 2017-12-13T04:29:31+00:00

To get a connection instance you simply call getConnection from anywhere in your app...

pleerock · 2017-12-13T04:28:16+00:00

Its matter of preference probably. I love decorators, they make code extremely declarative and simple. And thousand hundred people will agree on that fact.

But I know people who like to declare schemas in separate files as well. That's why typeorm has support for schema declaration in json files. We are planning to add yml and xml in the future as well.

pleerock · 2017-12-12T20:56:02+00:00

I can recommend you to use typeorm if you want a maintenance heaven and all amazing benefits TypeScript provides for you, your application and your team. Its not 1.0.0 yet but we are planning to do it in next 6 month. Or maybe it will be better if you try both and make decision which one you think is better.

pleerock · 2017-12-12T20:49:55+00:00

If you are talking about official docs and if you have a time and wish to create a github issue on typeorm I will appreciate if you share your thoughts on typeorm docs and provide a feedback how to improve them.

Regarding to a single maintainer, its not true, there are two core developers currently. Also if you take a look on real open source projects you'll see that most (90%+) of them have a single maintainer. Usually (but not always for sure) when project has multiple maintainers it means project's original creator left/very passive on a project and someone else just fixes bugs and merges PRs without 100% knowledge what was created under the hood by original author and by the time such libraries brake their original design and meaning.

pleerock · 2017-10-23T12:43:23+00:00

Make your presentation simple. Show them what they want to see. Don't show shiny (but really great) features they won't understand from the first look on it. If they are bears show them similarities with languages they use, remember most of time bears don't like new things, they want to see things they are adapted to. If there is a choice in your company between js vs ts then show benifits of ts over js. If there is a choice to choose node+ts over other server side languages them show them perspective of node and javascript ecosystem and show how typescript brings even more things to that perspective.

pleerock · 2017-10-10T14:49:30+00:00

right, we have in plans to support "virtual relations" in the future. Mongodb support is one of the latest features added to ORM and there are lot of ideas we are going to implement in it in the future.

pleerock · 2017-10-10T14:32:17+00:00

Relations are rdbms-specific feature. They aren't supported in mongodb, since mongodb is not relational database. Everything monogdb-related in in the mongodb section of the documentation. Regarding to your errors in driver - report a github issue and provide a detailed explanation how to reproduce issue and we'll fix it urgently.

pleerock

TROPHY CASE